One database to rule them all.

[PuddinPie]

I know, the title is cheesy but it work's so well to my question.
I was wondering if it was possiable to create a 'master' database that could control all of the setting's of other databases.

So, if you wanted to lock down a database, without having to worry about a password, you could open this master database and click on a button in a form and it would tell a different database to 'lock down'. Essentualy not allowing anybody to access it or the toolbars or function keys and stuff.

I don't want to use a password because they can be forgoten and if your away then you back up might not know it. I also dont want to MDE the backend either.

Has anybody heard of this or if it's even possiable or have I just gone round the bend?

Thank you.

 

[boblarson]

We currently use a similar system where I work. It is a database which has its backend linked to each database and there is code in each database which opens a similar main form which has a list box which lists all of the reports, queries, and forms available to the user and then it also has almost all of the potential criteria for those items there (so controls for start date, end date, Team member type, then team member name and much much more. But what happens is in this IT database we have, we add the reports, forms and queries to a table in that database for each linked database. We then can control which controls need to be filled out for which item and who gets to see any of the items. These are all done through junction tables and subforms on the IT Projects database.

So, yes it is possible. Depending on how functional you want it, it can take quite a bit to set it up but afterwards it is pretty cool and easy to add stuff.