1- What is the good of this if a user with a basic knowledge can go to “files/options/ current database” and make the navigation pane and ribbon visible again. They can still go to tables and change data.
If you hide the Ribbon using VBA, you will not be bale to go to Options.
Code:
DoCmd.ShowToolbar "ribbon", acToolbarNo
DoCmd.ShowToolbar "ribbon", acToolbarYes
2- If the ribbon is hidden through a VBA code, will “files/options/ current database” get disabled? I mean I want the “option” to be out of reach of the user. I mean user should only be restricted to work through forms and buttons.
Yes, the user will only see the forms. You can create custom Ribbons and leave the Ribbon visible but, I do not believe you will be able to hide the Backstage (File Tab) in a custom Ribbon (I could be wrong).
1- I did split it. The user opens the front end. But user can still make the tables visible in the navigation pane and ribbon and change data tables. It doesn’t matter if the user is working in the main access file or FE.
If you encrypt the backend (Make A Copy First), you can then link your FE file. If you link prior to encrypting the BE, it will not work. Also, as mentioned in this thread, someone with a real desire to get access to the Data Tables can.
2- I attempted to open the backend file. But it didn’t open. So I changed the extension in order to open it and encrypt it. After encryption, I returned the BE extension. But the front end is not working and asks for a password. I am totally confused
I do not understand why you would change the file extension of your BE file. It should remain accdb. In your FE file, delete the linked tables. Then, start the Import wizard to Link the tables again. The Wizard will ask for the pass one time.