Putting a password for a database

[emsadoon]

I have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.

 

[DavidAtWork]

Can I ask why you would want to password both BE & FE, if you design your database such that it will only connect to the back end on opening, then maybe you can get away with just one password on opening. If the user enters the correct password, the database will reconnect to the back-end and open as normal, if not it doesn't open.

David

 

[emsadoon]

Do you think the new encryption tool in Access 2010 is a better way to create a password than just having a username and password table in the database?

 

[scotwithadevil]

After you have split the database, open backend in 'exclusive' mode, use File tab to add password. Close backend. Open front-end in 'exclusive' mode. Use File tab to add password. With front-end still open, delete links to backend file(s). Use External Data tab to re-link to back-end file(s). On this occasion, you will be asked to supply the password for the backend file(s). Do that and then close front-end. Next time you open front-end, you will be asked to supply password for front-end but you will not be asked to then supply the password for the back-end file(s).

 

[emsadoon]

Can I ask why you would want to password both BE & FE, if you design your database such that it will only connect to the back end on opening, then maybe you can get away with just one password on opening. If the user enters the correct password, the database will reconnect to the back-end and open as normal, if not it doesn't open.

David

Thanks for your reply. But I do not want the user to open the back end file and make changes to it.

 

[emsadoon]

After you have split the database, open backend in 'exclusive' mode, use File tab to add password. Close backend. Open front-end in 'exclusive' mode. Use File tab to add password. With front-end still open, delete links to backend file(s). Use External Data tab to re-link to back-end file(s). On this occasion, you will be asked to supply the password for the backend file(s). Do that and then close front-end. Next time you open front-end, you will be asked to supply password for front-end but you will not be asked to then supply the password for the back-end file(s).

Thanks for your reply. Do you know how to delete the link between front end and back end.

 

[scotwithadevil]

Hi
The user won't be able to open the backend file and make changes to it unless you supply them with the password. The password for the front and backend(s) doesn't have to be the same so you need only give your user the front end password. (You, as the designer, will only be asked for the backend password the first time you set up the link between the front and backend(s)).

To delete the links between the front and backend(s), display the tables in the navigation pane using F11 and then just delete them - this will delete the link, not the actual tables. The use 'External Tools' tab to re-link to correct tables or to import them instead (but it is better to keep the tables in a back-end and link to them rather than import them into your database front-end).

 

[emsadoon]

When I delete the linked tables in my front-end, then the Linked Table Manger button will be disabled. So I cannot re-link the front-end to the back-end. Do you know where I am going wrong?

 

[emsadoon]

Sorry. I was confused and was looking for a wrong way to re-link the tables. I made it work by going to the External Data Tab, and then Access button, and then link option. Thanks Scotwithadevil for your suggestions.

 

[DavidAtWork]

"Thanks for your reply. But I do not want the user to open the back end file and make changes to it"
They won't be opening the BE file, I meant they enter a password to open the FE file and if successful, it reconnects to the BE
David

 

[scotwithadevil]

You're welcome. Glad to see you worked out that Linked Table Manager is only available once you have linked the tables so you do need to use the External Data Tab to link the files first. However, once they are linked, you can use the Linked Table Manager to change the location of the linked backend files - useful if you are swapping from test back end files to live back end files - with the 'always prompt for you location' and 'select all' options on. Good luck with your db!