Urgent question on locking files

[themastertaylor]

I've just built a database for a friend's business, to be used by 3 simultaneous users. I just split the database and sent the front and back end across to him, the back end is in a shared folder and each user has a local copy of the front end. the problem is that only one of them at a time can access the system - i'm assuming that its in some sort of lock mode. any idea how to fix it before they kill me?! we're all running access 2007

Thanks in advance

 

[maxmangion]

check that the database is not being opened in "exclusive mode".

 

[themastertaylor]

check that the database is not being opened in "exclusive mode".

i can't see an option in the options menu for the specific database but access as a whole is set to open in shared mode with no record locks

 

[namliam]

Tools => Options => Advanced tab

The option to open "Shared" or "Exclusive" is there as pointed out by Max

 

[themastertaylor]

Tools => Options => Advanced tab

The option to open "Shared" or "Exclusive" is there as pointed out by Max

thats the option i meant - its definitely set to shared with no record locks - what i meant was that i was unsure if there was an option hidden away under the current database menu

 

[themastertaylor]

just been over to have a look at the problem, the back end is in a shared folder on a 4th machine, all 3 users have their own machines running vista and office 2007. all have their own FE stored locally and access is set to open in shared mode. i found a site yesterday that suggested opening the FE from a shortcut causes access to open the database in exclusive mode. I tried opening access on each machine then browsing to open the FE. the first machine will load the database, then any other will come up with an access not responding message. as soon as the first user closes the database one of the machines displaying not responding will instantly load the system.

any other ideas on the problem? - its got me completely stumped!

 

[namliam]

It sounds to me like the hosting computer doesnt allow the multiple connections some how...

I am not good with security issues... but... sounds like...

 

[georgedwilkinson]

The easy way to test that is to create a quicky BE with 1 small table, a quicky FE lined to it, put the BE on the "server", and try to connect while one of the others is connected. If it connects OK and you can manipulate the table, then the "server" allows concurrent connections.

Just to set the record straight, you can open the FE from a shortcut and it will not open the BE in exclusive mode. Now if more than one person uses a shortcut to the same FE, yep, you got problems. But you clearly said that's not happening.

 

[themastertaylor]

The easy way to test that is to create a quicky BE with 1 small table, a quicky FE lined to it, put the BE on the "server", and try to connect while one of the others is connected. If it connects OK and you can manipulate the table, then the "server" allows concurrent connections.

Just to set the record straight, you can open the FE from a shortcut and it will not open the BE in exclusive mode. Now if more than one person uses a shortcut to the same FE, yep, you got problems. But you clearly said that's not happening.

Thanks for the idea, tried it last night and it turns out the network is the problem. i had a quick play with the sharing settings and managed to get 2 users on at once, just a problem with the third now. its a tough one as i've never used vista myself and their network behaves strangely, all users can access each others files except user a can't get into user b, but b can gain access to a. if anyone has experience of the best way to share a file in this manner in vista it would be much appreciated as trial and error is a bit of a no no given they need the network to remain operational for work.

 

[georgedwilkinson]

Ugh...Vista sucks. Your company was brave to install it.

Not sure if you have this luxury, but I turned off all Vista security soon after I brought my PC home. It causes all kinds of issues with files you "think" you want to use. I guess in this case, MS thought they knew better.