password for navigation pane

[imdl]

hi, i have created a database being used by around 50 people. for security of forms and queries, i can hide the navigation pane through the office button > access options > current database > uncheck Display Navigation Pane. however, i need 3 people to have access to the navigation pane to be able to edit tables and create/edit queries. is there a way to set-up a password to activate the navigation pane?

regards,

imdl

 

[HiTechCoach]

hi, i have created a database being used by around 50 people. for security of forms and queries, i can hide the navigation pane through the office button > access options > current database > uncheck Display Navigation Pane. however, i need 3 people to have access to the navigation pane to be able to edit tables and create/edit queries. is there a way to set-up a password to activate the navigation pane?

regards,

imdl

if this is a multi user database theb the app should be split. Editing of tables will be done in the back end.

I recommend using a mde/accde for the front end since each user should have their own copy.

you make changes in the master mdb/accdb. Create a new mde/accde that is deployed as an updated front end.

 

[imdl]

thanks for your help. i was able to split the database and create a back-end database where i can update tables. it works, when i open the front-end database, i could see the update.

however, when i tried creating a query on the back-end, it does not show up on the front-end. is there a workaround on this?

we need to create queries from time to time, and we do not want users to display the navigation pane, to protect the objects.

imdl

 

[HiTechCoach]

thanks for your help. i was able to split the database and create a back-end database where i can update tables. it works, when i open the front-end database, i could see the update.

however, when i tried creating a query on the back-end, it does not show up on the front-end. is there a workaround on this?

we need to create queries from time to time, and we do not want users to display the navigation pane, to protect the objects.

imdl

The back end only has tables. This is also where you create the relationships. To make table design changes you do that in the back end. All the shared data is stored in the tables in the back end.

The front end has all the other objects except the shared tables. In the front end you create linked tables to the shared tables in the back end(s). There can be multiple back ends. All the forms, reports, queries, etc are all in the front end. There is no shared data stored in the front end.

You can have multiple front ends all linked to the same back end(s) that have different functionality.

You can lock down the front end so that the users can not get into the design of the front end. I use an MDE/ACCDE.

I also force the front end to be opened with Access in runtime mode. In Access 2007, you can rename the extension from .accde to .accdr and Access will start in runtime mode.


Hope this helps ..