Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
KnooKie
Aged Yak Warrior
623 Posts |
 Posted - 2005-04-04 : 12:13:27
|
| Access 2003.i have written an access database for a friends company (5 users). The backend is on their server (S drive) and they each have an MDE frontend on their machine (C drive) linked to the backend.Some of them get a message when they try and open the frontend a long the lines of (can't remember the exact message)....'Cannot Open S:\Backend.mdb it is locked exclusively by another user'The first person can open the frontend with no problems but subsequent people trying to open the frontend get a similar message to the one above. They do have one guy however who can get in the frontend after someone else is already in from whichever machine he logs in to.they have logged a call with their remote support people but it seems to be taking a while for a reply, which means they can't use the database properly until the situation is resolved.Does anyone have an idea what may be the cause ? I don't know a great deal about windows security but am assuming it may be that the guy who can get in has admin rights on every machine ? Thoughts ? Not sure about the others though ? Ideas ?i have not used any Access security at all so can't be anything to do with this.any insights greatly appreciatedPaul====Paul |
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2005-04-04 : 15:41:20
|
| Is this an access or a SQL backend?JimUsers <> Logic |
 |
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2005-04-04 : 23:37:22
|
quote:
Originally posted by JimL
Is this an access or a SQL backend?JimUsers <> Logic
quote:
'Cannot Open S:\Backend.mdb it is locked exclusively by another user'
I guess we could assume a JET backend.It could be a number of things - I guess its possible its a permissions thing, but not sure what you'd look at other than making everyone's permissions the same.Alternatively, you could be just unlucky, and it may be that the front end is holding open some connection which is locking other users out - it sounds like to me you need to do some more testing to be able to replicate the problem at will....--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2005-04-05 : 05:42:20
|
| yes it's an Access backend.i've tested it on another company network and it seems to work for people who are administrators of their machine but otheriwse not.====Paul |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2005-04-05 : 08:40:36
|
| The best solution would be to upgrade to SQL Backend in the long run you would be much better off.JimUsers <> Logic |
|
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2005-04-05 : 09:06:17
|
| are you sure that non-admins have "Change" persmissions to the folder that the Access MDB file is located and not read-only?- Jeff |
|
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2005-04-05 : 09:18:04
|
| no i don't think non admins have change permissions to the folder although the first person into the database can happily Add/Edit/Delete data. It is just that subsequent people going in get a message that similar to the one i posted earlier. Only one other person can happily get in after someone is already in and he has full admin rights as it's his company.I am thinking that they will need to check that everybody has Read/Write/Create/Delete permissions for both the backend .mdb on the server and also for the folder it is in. This is a guess though.It's annoying as i think the database is ok but they can't use it (and subsequently pay me) as things currently stand.====Paul |
|
|
|
|
|
|
permissioning problem ?