MS Access 2002 hangs when a server is shut down

[pisaac]

Hi,

We have recently migrated our Domain Controller from Server X to Server Y. We have down graded Server X using dcpromo and uninstalled all networking components for windows 2k advanced server. We have a MS Access 2002 database (data.mdb) on a shared drive on Server Y where all of the tables are stored. Everyone accesses the database using a local database (local.mdb) which is linked to tables in the database in the shared folder. When we shut down server X and open the local database on a client XP computer the application hangs, however the application runs OK when server X is on. Has only got any idea why this is happening.

Thanks in advance,

pisaac

 

[hymn]

Have you relinked the db on the local machines to the new server?

Hope this helps
Hymn

 

[pisaac]

Yep,

after about 5 mins of waiting for the egg timer to go I finally get into the database (which takes about 5 mins to do any single action) I can then re-link the database, this doesn't fix the problem. I've even tried to copy the data.mdb file locally and re-link the tables to the c:\ drive but the same problem continues. It seems as though server X is supplying some service(s) which allow the database to work regardless of where the data.mdb file is located... AAAAAHHHH!!!!

 

[hymn]

The only over thing that I can think of is that someone has hardcoded something to that server

Hope this helps
Hymn

 

[pisaac]

Can't think where the autoexec macro points to a small piece of code which i've remarked out ('), then loads a login form which has no OnLoad code. The mind boggles..., might try creating a news domain but that would be a pain, has anyone got any other ideas?.

 

[willir]

Hmmmmm

Check for hidden linked tables.
Check for loading any auto modules.

First rather, than working with the server Y copy of the database, save yourself aggrevation and work with a copy.

Now here is something to ponder...
- Linked tables will not cause the application to hang until the table is accessed. And then you should only see a time out error.
- The start up module can be set via the Access Menu "Tools" -> "Startup", and does not have to reference an AutoExec module, macro or form.
- A developer may add code to re-linked unlinked tables. Hmmmm. What if the location is new and not expected per the code. If this code tries to re-link and fails with no proper error checking, or a loop - I can see this causing problems.
- HOLD down the SHIFT key when you open the database. As long as the database does not disable this feature, you will open up the database without running / loading anything.

Richard