Database Shutting Down Unexpectantly

[Williams]

I have a database that is stored on a network and used by approx 5 people. 1
user is having problems with MS Access shutting down unexpectantly. I have
tried to repair the database on her workstation, but the behavior continues.
Any ideas on how to rectify this situation?

Thanks.

 

[Jeff Boyce]

Which version of Access?

Is the database "split", with the data on the network and a copy of the
'front-end' on each user's PC?

Are there any "Timer" events in the forms?

Is there any commonality in WHEN it shuts down? That is, what is this user
doing when it quits?

Can this user log onto the application on another PC and not have the
problem?

(just a few of the questions you'll need to resolve to troubleshoot this...)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Williams]

1. Access 2007

2. Database is not split. Data and objects in same file on the server.

3. No timer events on forms.

4. Shut down appears to be random. (Example: Updating data, closing
forms/tables, viewing reports, etc.)

5. I'll have to have the user logon to another computer to try this out.
But my assumption is that it is with her specific computer since the other
users are not encountering the same problem.

 

[Jeff Boyce]

Interim observation ...

Having a single database file located on the network and shared by all users
is NOT recommended.

Not only does this require each user's PC to download all the form/query/...
definitions/information (the network folks frown on this), doing this
greatly increases the risk of corruption of that (single) file due to one
user 'bailing out', a flakey NIC (network card) or network plumbing, and
other factors.

The preferred design is to "split" the database, with the data residing in a
single file on the "back-end" (your network location), and a copy of the
front-end (everything but the data) residing on EACH user's PC.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Williams]

In regard to this issue...are there any known glitches that would cause the
lone users workstation to shut down. I realize that not splitting the
database increases the likelihood of corruption due to the one user
haphazardly shutting down, but I need to know why they are shutting down if
the database is not corrupted.

 

[John W. Vinson]

In regard to this issue...are there any known glitches that would cause the
lone users workstation to shut down.

Sure: a noisy NIC (network controller) on their box. This would be a prime
candidate for both random errors (including shutdowns) and random corruption
of the shared database.