Access bugs in multi-user environment?

[GWhiz]

Hi, folks!

Am using Access 97 with two computers. When one is running a form whose record source is table X.....the other computer gives a "File already in use..." error when running a form also based on table X.....even if there is no editing going on, or they are accessing different records. Error will not clear as long as both computers are showing a form based on a shared table, making it impossible for both users to work simultaneously, even on different records.

Have tried using both split tables, and un-split tables. It could be a "nut loose behind the keyboard" error (probably is).

Any ideas?

Thanks, folks.......y'all are the best!

Respectfully,

GW

 

[pcdaveh]

What do you mean that you have split the tables? Do you actually mean that you have a split database?

 

[GWhiz]

PC:

Ty for your response.

Yeah......have split the database, creating a "X_be.mdb" version in addition to the original "X.mdb". Have linked tables both ways from remote computer, to the Y table in X.mdb database (before it was split), and to the Y table in the X_be.mdb database (after the split). Can get remote computer to see Y table either way......but only if main computer (not really a server, just the computer that contains the table I'm linking to) is not also displaying a form whose record source is the Y table.

If remote is running a form based on the linked Y table, main computer shows "cannot link, file already in use" error when I try to run a form on the main computer. If the main computer is running a form based on Y table, then remote shows "cannot link, file already in use" message.

Have verified that Access is running in "shared" mode by default.

Not sure what I'm doing wrong here......if anything.

Respectfully,

GW

 

[lameid]

On each computer go to the tools menu select options.
On the Advanced tabe make sure Default Open Mode is shared and Default Record Locking is set to No Locks.

If that doesn't work...
Also make sure both users have the same permission to the foder the database is in... Maybe log in as the same user on both machines and test concurreny. Network file permisions can cause problems with file locks on the .ldb file which needs to be updateable to maintain record locks (technically page locks). If one user has read permission to the folder then that user has a read lock and a user with change permission can't access the file. If a user with change permission is in the database, the LDB file gets created but the other user can't change it so he can't log in. So one type of permission logging into the database locks the other out... interestingly enough as many as the same type of permission can log on as you like.
As long as the permission to the folder is set to change for all users you can set the file permissions however you want.
WARNING: Compacting and Repairing both create a NEW file with the same name which means the new file inherits the less secure permissions of the folder. On the plus side, only those with change permission can do this.