Hello,
I have an application and BD.mdb (Access97) on the server (Windows2003 EE)
with fifteen workstations (Win2k & WinXP), which run the application by
mapping the share on the server. The problem is that after some user run
the application and after doing some job, they don't close the
application, but after some time another user can't run it, because of the
BD is in suspect mode (information from LDBview).
My question is: what is the reason of this? Corrupted NIC, LAN? Maybe bad
settings in ODBC, Registry etc.?
Please, help...
Thanks for all,
OliP
Tony Toews - 19 Apr 2005 16:42 GMT
>I have an application and BD.mdb (Access97) on the server (Windows2003 EE)
>with fifteen workstations (Win2k & WinXP), which run the application by
[quoted text clipped - 5 lines]
>My question is: what is the reason of this? Corrupted NIC, LAN? Maybe bad
>settings in ODBC, Registry etc.?
Unfortunately there could be many causes of the leaving the MDB in
suspect state.
I'd suggest trying to see if one workstation is consistently causing
this problem or many. There's a lot of things to try and to figure
out to isolate this problem.
See the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm