Deploying a Multi-User Access Database with Different Needs on Different Front Ends

[Sue999]

I've split the database and want to link different versions of the front end to the back end from 4 different users, giving each different access to the tools, ribbon and quick access toolbar according to their needs/rights.

I've tried copying the front end for each user but it just replicates and any changes to the options (eg the user name and initials, hide the Navigation Bar etc) are carried out in all versions. It's obvious that, even though I carry out the changes in the front end, the changes relate to options in the back-end database to which the front end is linked - even importing all the front end objects into a new database doesn't solve the problem. As long as the new front end is linked to the same back end, the options must be the same for all users.

I've created and set up a 'secure'(!)logi n procedure that identifies users individually and by groups and that works well for initialising the correct startup form according to user group. Is there any way I can restrict programatically which users have which global options on the back end database?

[Sue999]

I've just done a bit more testing and even without links to the back end tables the front end still replicates changes.

I tried looking on File/Options/View and 'Edit database properties'. On the tab 'Custom' the properties list at the bottom of the popup window shows a property 'Replicate', set to 'Yes'. I tried deleting this option and rebooting Access but the front end still replicates and does not allow customisation. Is there anything else I could try?.

[Sue999]

Having now tested a completely blank database in comparison with the front end, I realise the problem lies outside the scope of individual databases and relates to the application itself. I suspect that even if I changed the options within the API I would be unable to make any difference.

However, I have been doing the testing from within my own system so I do have some hope that when I install the front end on the machine of a user who has Access installed I shall be able to set the options within their instance of the application and get round it that way. Can anyone confirm that this is correct? Thanks.

[Rabbit]

You are correct. Those settings are at the application level. You can, however, use VBA to change those settings at run time. So that no matter which computer it's on, when they run the database, it will change their application settings. Just be aware that whatever settings you change, the user can change back.