Sharing properties of a single mdb file affected by user

[limperger]

Hello everybody!

I have just found out that the sharing properties of a single database (mdb file on a network), accessed by 3 users, change depending on the user accessing the database. That is, with the file opened by 2 users at the same time, in my computer, the sharing properties appeared as set to share (not exclusive) and single entry-lock. Nevertheless, in the computer of the other user, the sharing properties are set to exclusive mode and an all-entries lock. Why, with a single file (neither splitted nor working with linked tables and different files), the Sharing mode change depending of the user? And what is worse, why the sharing properties differ even with 2 users having the database opened at the same time? Is Access trying to make a fool of us??

Best regards from Barcelona

[Stewart Ross]

Hi. I suspect that the user in question does not have Create rights to the shared directory in which the database is located. As an MS Knowledgebase article linked here states, if the shared .ldb lock file cannot be created the database will be opened in exclusive mode by that user.

The user rights required for each user of an Access database placed in a shared directory are Read, Write, Edit, Create and Delete.

-Stewart

[Stewart Ross]

Hi again. I have now closed the previous thread which you started on this topic on 3 April. It is not good practice to create duplicate threads if you don't get a reply to your first post. All you need to do is to 'bump' the topic by posting a reply to your own question asking if a contributor could look again at your issue.

-Stewart

[limperger]

Hi Stewart:

First and foremost: let me apologise for any inconveniences caused by this second post. I wrote it again so as to provide new information.
Second, I don't know if what you're commenting is de tools>security>group and users permission. Is that it?

Thank you in advance

Best regards

[Stewart Ross]

...Second, I don't know if what you're commenting is de tools>security>group and users permission. Is that it?...

Hi limperger. No worries on the second post - if you are faced with a similar situation in future just add the new data as a new message in the original thread.

What I am referring to is not the Access security tools; it is the network folder permissions granted to the user who is locking the database. This is nothing at all to do with Access; the permissions are granted by whoever administers your network when their accounts are created. As mentioned, a user must have create access rights to the shared folder in order for Access to create its .ldb lock file.

-Stewart

[limperger]

To the best of my knowledge, the network setting grants every user an administrator status, so as to be able to do every action required.
But even more incredible now.... I have just tested, with the user having this problem (and with his account), the database sharing performance and I have been able to open the file after he has opened it in the first place. This situation suggests me that the real problem has to do with the computers used (this particular user uses 3 different computers to access the database), rather than the network setting (which, I repeat, should be set as "administrator status" by default). Am I right? Any wonder why is this happening?

Best regards from Barcelona

[limperger]

New information coming!!!

Surprisingly, now that this user has typed some data into the database (using a form), I am not able to open the file. That is, in the previous situation, I have opened the file with his account and I have been able to do the same with mine. But no data has been typed. But soon afterwards, after hearing him typing some data into the data base, I have tried to open the file again and, to my surprise, I have not been able to. I have checked the sharing properties (in case in his Access session might had spontaneosly changed), and remain as specified (shared and edited-record lock). Please note here that there is no front-back end database splitting.

This situation is wearing me down!!

Best regards

[Stewart Ross]

Hi. Make sure that everyone else is logged off from the database then log your user with the lock problems in to your database. If he has the correct permissions you will see a file called <yourdatabase>.ldb in the same folder as the database, with time of creation the time at which your user logged in.

If you do not see such a file there is a permissions issue, regardless of what you are telling me about his administrator status. Could you check this please

The .ldb file is updated for each new user who logs in, and is automatically deleted when the last user logs out

As mentioned, no ldb file equals no shared access.

I have attached a small screenshot from one of my shared databases called Staff which shows the Staff.ldb lock file, so you can see what to look for in your shared folder.

-Stewart

[limperger]

Stewart:

I confirm you that a ldb file appears everytime any of the users log on the database. And another aspect of interest: this problem seems not to appear between me and the other user (not the one with this problem), that is, I am able to log on irrespective of he typing data on the database or he accessing the database in the first place.

Best regards

[Stewart Ross]

Sorry, limperger, there is no more I can suggest at present. If your user can create an LDB file, and the network rights are the same as everybody else, and there are no specific security settings which have been changed, I am out of ideas as to why there should be any differences in record locks for one specific user, or why you should be able to access and update the DB at all times when others cannot.

Perhaps other contributors may be able to help

-Stewart

[limperger]

Hello Stewart:

First and foremost: Thank you for your help. It is much appreciated indeed!
Secondly, let me sum up the situation, so as to get the picture clear.

1) As confirmed by the computer ' technicians here, everybody is granted an administrator status in the network. So if, as you confirmed, the permission setting you were talking about has nothing to do with Access itself, then the problem should not be due to the network account.
2) I checked the Access file, once locked its access for the rest of us, opened by the user with this problem. The Tools>Options>Advanced were as specified: shared status and edited-record lock. Also, the form properties were set as edited-record lock. In short, no changes in here.
3) Could there be any changes in the ldb file, as the session progresses? I mean, is it possible for the ldb to experience any change in its properties? Maybe, if this should be the case (I have no idea), I could check its properties and shed some light on the problem. Anyway, what is clear is that the ldb appears for all users.
4) There is no FE-BE split. I would try to do it and see if there is any improvement. Could the FE-BE division help in here?

Thank you very much in advance

Best regards

[limperger]

Hello everyone!

With the splitting of the database, the sharing problems are over. DB splitting is, therefore, strongly recommended for everyone!

Best regards