Mulituser problem - strange

T

Tim

Hi

We have just started to encounter a problem with a couple of our multi-user
access applications (written in Access 2.0). These applications have been
running smoothly (up to 11 years in one case) but just recently have been
causing a problem.

When a user opens there copy of the their front end they occasionally get
the message 'Couldn't open file .........' (where ........ is the UNC name
of the backend). The back end files are not marked as corrupt and do not
need compacting.

Sometimes, if the user closes the file and then re-opens all is fine,
otherwise, we have to get all users to close their front end copies. Once
they have done this the problem is rectified and all users may access the
system normally.

Has anyone else experienced this or have an idea what is causing this
problem?

I had an idea that it is linked to the .ldb file in some way and have
noticed an increase in traffic on the server these systems are located. But
don't know how to test this? Could a delay in disk read\write be a factor?

Any thoughts would be most welcome


Tim
 
D

david epsom dot com dot au

Are you using Access 2000+ on these files at all? Jet 4.0 has caused
some problems when mixed with Jet 2.5

(david)
 
F

Frank Konzal

I suspect something has changed - service packs, new operating systems, etc.
 
T

Tim

David

We are not using Access 2000 or above on any of these files to open or
attach to them.

However there are some machines that access these files using Access 2.0
full version, on machines that also have Access 2000 runtime installed on
them.

No service packs have been installed or changes have been made immediately
prior to these problems occurring. Obviously over this period there have
been operating systems changes and these have not caused any problems.
These problems have occurred after a long period of stability using the same
operating systems\service packs.

Any further help would be greatly appreciated.
 
T

Tim

Thanks David.

I will read through these documents, implement if appropriate and continue
to monitor. We are using Win 2000 Server not 2003 but this appears to be
the case also on 2000.

I hope this will solve our problems.

Regards

Tim
 
Top