Record Locking

[miacino]

I just built a database that will be used by about 10 users. V 2016. When one person opens the database, it is fine. When a second person opens they get the error that they cannot open ("you do not have exclusive access to the database at this time"). Under client settings, I have default open mode = shared. Default record locking = no locks. I unchecked "open database by using record level locking".

The database does have a simple password to open the database - is this causing the issue?

Thanks for any help!!
Michele

 

[gemma-the-husky]

not sure what is in the link - however.

you are ALWAYS best advised to split the database to a code (front-end) database and a data (back-end) database, and then ensure that each user accesses a distinct copy of the front end. No sharing of front ends.

 

[miacino]

I did split the database. Back end of tables. Front end of forms etc. When the second person attempts to open the database it gives that error message - you click OK - and it gives you the error 10 more times. (ironically the number of tables?). It then lets you in and lets you edit.

 

[miacino]

I do need them to share the front end or every time we make an edit to the form or add a tracking field or anything, I'll have to give an updated copy to each user.

 

[gemma-the-husky]

I do need them to share the front end or every time we make an edit to the form or add a tracking field or anything, I'll have to give an updated copy to each user.

but yes.
that's what we do.

 

[The_Doc_Man]

You get forced into exclusive access if the folder permissions are not correct. All users of this app have to have Windows MODIFY-level access to the folder and all files in it, and probably any child folders/files as well. The reason you get this is that the second user cannot open the .LDB file (or more modern equivalent) due to those faulty permissions.

Just guessing, but I've seen that happen before so it isn't a blind guess.

 

[jdraw]

I agree with the others:
-you have a separate backend (tables)
-you have a "standard" front end and you put a copy of that front end on each user's PC

As for changing a Form etc, that should be a relatively infrequent occurrence since you have a tested
and accepted operational/production database. If you must make a change to the front end, you take copy of your standard front end, design and develop your changes on this copy; test it thoroughly and "deem" it suitable for Production. You then make a copy of the "new standard" front end available to the users.

There are many posts and articles regarding techniques for deployment of a new front end.

Bottom line, do not directly use production for making ad hoc or "simple" changes like

an edit to the form or add a tracking field or anything

. Treat production as critical to your business. Set up and communicate standard procedures for the "safe keeping" of your business and assets.

Good luck.