If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database Shutting Down Unexpectantly
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. |
#2
|
|||
|
|||
Database Shutting Down Unexpectantly
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" wrote in message ... 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. |
#3
|
|||
|
|||
Database Shutting Down Unexpectantly
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" wrote: 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" wrote in message ... 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. |
#4
|
|||
|
|||
Database Shutting Down Unexpectantly
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" wrote in message ... 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" wrote: 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" wrote in message ... 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. |
#5
|
|||
|
|||
Database Shutting Down Unexpectantly
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. "Jeff Boyce" wrote: 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" wrote in message ... 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" wrote: 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" wrote in message ... 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. |
#6
|
|||
|
|||
Database Shutting Down Unexpectantly
On Tue, 7 Jul 2009 11:24:01 -0700, Williams
wrote: In regard to this issue...are there any known glitches that would cause the lone users workstation to shut down. Su 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. -- John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|