LDB Viewer (JetUtils)q

[Tim]

Hi

I've been experiencing a problem view a couple of Access 2.0 databases which
behave strangely from time to time (new problem after being stable for over
5 years).

The front end database can not open the back end database (all users have
their own local version of the front end), the user gets 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. If all users currently using the database close their front end
then the problem goes away and all users can the attach correctly.

When checking the ldb file using LDB viewer I have noticed the following;
when there is no problem the viewer shows users and it appears to be able to
read the data in the ldb file correctly, however when this problem occurs
the ldb viewer can not see\report on any users connected. In fact there is
a message in the bottom left hand corner stating '-1 users in database',
however this is not the case as checking the files open on the server there
are multiple entries shown as having the mdb and ldb files open.

Any ideas of what to check and or change?

Many thanks

 

[Monte]

I would look for some change in the security associated
with the network path to the LDB location. All users
accessing the database need read/write/create/delete
permissions on the share.

 

[Tim]

All users do have read/write/create/delete permissions on this network
share, directory and files.

 

[Cynthia]

I have been having a similar problem. 2-4 users will be using the shared
database and new users will be blocked from logging on. A message will
appear saying that the database needs repair, would you like MS to repair?
If one says yes then a message says that you cannot repair because another
user has the database locked. (This user is for real but is not locking
anything.) I have everyone get off, I get in and repair and we are up again.
This has been happening frequently just of late.

 

[Tony Toews]

I have been having a similar problem. 2-4 users will be using the shared
database and new users will be blocked from logging on. A message will
appear saying that the database needs repair, would you like MS to repair?
If one says yes then a message says that you cannot repair because another
user has the database locked. (This user is for real but is not locking
anything.) I have everyone get off, I get in and repair and we are up again.
This has been happening frequently just of late.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
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