Access 2.0 database and Windows XP

[JGG]

We have a Visual Basic 3.0 application running against an
Access 2.0 database in peer to peer configuration, with
one of the systems hosting the database. This solution has
worked fine over Windows 3.11 and Windows NT4.0. Recently
we've upgraded all the operating systems to Windows XP Pro.

After this we've begun to experience "Couldn't lock file
SHARE.EXE hasn't been loaded" errors when trying to open
database from our application or from Access 2.0.

I've disabled opportunistic locks in all machines.
I've reviewed folder permissions for database folder and
all the user have all the permissions in this folder.
I've searched google forums, Microsoft KB articles with no
success.

When the error appears I close our application in all the
machines in the network (which closes database connection
and sets the object to Nothing) and after that all the
users can open the database.

The error doesn't happen always so it's really difficult
to troubleshoot it.

Some of the machines have Office 2000 installed.

Any hint?

Thanks and best regards,

 

[Allen Browne]

Wow. It's been years since I've seen this error, but it probably has to do
with a read-only ldb file, or possibly read-only network share.

Check the folder where the mdb file lives. If there is also and ldb file
with the same name while Access is not running, delete it. Right-click the
mdb, and ensure it is not read-only also. (It may be if copied from a CD.)

Further information:
http://support.microsoft.com/default.aspx?scid=kb;en-us;116387

 

[JGG]

Hi Allen,

Thanks for your answer. I've checked your suggestions with
no success. I can't explain why the error happens randomly.

Thanks,

 

[Allen Browne]

Is the database split, i.e. shared data file; separate front end on each
workstation? If not, that should help.

Is there anything specific that triggers the issue?

 

[JGG]

Hi Allen,

The database has no code at all. It behaves just like a
database and our front end is a Visual Basic application.

I suspect the problem could be due to any of these reasons:

* Office 2000 installed in some machines.
* Depending on the order that machines connect to the
database, the ldb file is created with different
permissions.

I'm trying to make some tests and I'll inform you.

Thanks and best regards,