Can I edit in the Backend Access database while other users are in the front end .accde file

[pbDudley]

Hello

I have created a database in access that has a front end .accde file and a back end .accdb to store the tables, I've linked all of the tables to the front end.

If I want to go edit the tables in the back end does this create issues if users are currently logged into the front end .accde?



And if so If I make a copy of the back end and name it differently is this not connected to the front end, only the one database that I actually connected to the front end?

I had one user state that what he entered wasn't saved but I'm hoping that was an error on the user and not because I was in the backend but I'm not sure

Also this is a test run for me and the users and for now Ill go and delete the .accde file, make my edits to the back end and front end then re-create the .accde file but Im trying to see how to work in it without issues

and lastly I assume the .accdb file prior to being converted to .accde I could just import the tables so they arent linked but I just see that causing issues if im not careful

[moke123]

when you have a table open in design view I believe you have exclusive access so the user would get an error message.

[pbDudley]

Ok, I can test and see if this happens when someone is in it.
I can just get in the habit of working on it when no ones in it for I assume, thanks for the response

[pbDudley]

Do you think if I just make a copy of the back end and work in that its fine? that front end should only be connected to the one that i used to link the tables in and if i have a copy of the back end and its all the same i should be alright?

[Welshgasman]

What do intend to do? as that copy will very quickly be out of date, data wise?

[Micron]

If I want to go edit the tables in the back end does this create issues if users are currently logged into the front end .accde?
Depends on how locks are applied to tables. As noted, a table in design view is not accessible to anyone and that may raise errors to the user. A table being edited may raise a warning to user or you when you try to save the record being edited, if that's what you'd be doing.

And if so If I make a copy of the back end and name it differently is this not connected to the front end, only the one database that I actually connected to the front end?

I had one user state that what he entered wasn't saved but I'm hoping that was an error on the user and not because I was in the backend but I'm not sure
did user get a warning or error message?

Also this is a test run for me and the users and for now Ill go and delete the .accde file,
unless you are altering the front end it's not necessary to recreate fe for be edits
make my edits to the back end and front end then re-create the .accde file
and lastly I assume the .accdb file prior to being converted to .accde I could just import the tables so they arent linked
keep tables in be; wise to back up the be periodically with a different file name (up to you to decide on the frequency) not advisable to keep splitting db if that is what you mean

Research on how to log users out of the fe when you need it. I used to set a checkbox in a be table field. FE code looked for that flag every 10 minutes (I think) and if set, users were notified maintenance was in progress and they could not open the db. The 10 minute counter was a fe variable that subtracted x minutes every time it ran. At zero, fe closed.