A97 on NT to A02 on XP - Errors

[Bonnie]

Used to have A97 on NT server, now have A02 on XP. Have 30-
50 folks using various DB's ALOT. There could be up to a
dozen in any one file at different times. Always been like
that. No real changes in usage.

I now get frequent reports of errors (and get them myself)
enough to drive me bonkers. We are getting them in most
applications, including Access, but it's affecting my
DB's. A few times, I have had to refresh my table links.
Sometimes, a copy of the file with _Backup added to the
name appears after one of these errors.

The error dialog box says: Microsoft Access has
experienced a problem and needs to close. We are sorry for
the inconvenience. If you were in the middle of something,
the information you were working on may be lost. CkBox--
Restart MS Access - Please tell MS about this problem. We
have created an error report that you can send to help us
improve MS Access. We will treat this report as
confidential and anonymous. To see what data this report
contains, click here. Btns - - Debug - - Send Error
Report - - Don't Send.

Can anyone shed any light? I ask systems and they think it
has to do with multiple users but I try to explain that
Access is made for multiple users. Any help or advice
would be most welcome and appreciated!!! Thanks!

 

[Wayne Morgan]

I don't know if this has anything to do with it, but I believe that WinXP,
like NT4 workstation, is limited to 10 users connecting to it at a time. Is
there a chance that the connections are being refused or broken by this
limitation?

 

[Guest]

Hi!

We had very similar problems until we found out that it
might be the local virus scanners on your workstations. If
you have application mdb's and data mdb's. The virus
scanner attempts to scan the local file generates locks
and causes the database to crash. After configuring the
virus scanner not to scan md*-files we had no more
problems.


Kind regards
Gabriel