Securing multiple databases 1

[hanosm]

Hi,

I have created several databases for the office in which I work. However, not knowing what I was doing, I secured each them using a different Workgroup Information File.

Since then, I have been informed that I can use one WIF for all the different databases, all I have to do is set the different permissions for each one. This would mean that users don't have to keep joining different WIFs everytime they open a different database.

Unfortunately, all I have are the secured versions of the databases. I have deleted (for some STUPID reason) all the unsecured databases (figure I wouldn't need them - duh!). I have all the administrator log in details for all the databases, but I'm not sure how to re-secure them using the new single WIF.

Any ideas would be greatly appreciated!!!

 

[psemianonymous]

The most important thing to remember is that you have to change ownership of each object in the database. This basically means that you will have to 'import' each object into the new secured database using your superuser account.

Your superuser account may not have enough permissions to get into your old-secured databases. If so, log into the old-secured databases with the 'old-superuser' and export all objects to an intermediate database file (presumably not secured). Then have your 'new-superuser' login import all objects from the intermediate database.



The other thing to note is that your workgroup file is just like any other database file in that you shouldn't overload it with too many users. I'd recommend that you keep a 'master' WIF and propogate any changes to this by copying over each application's copy of the WIF. This way, you don't have users logged into all your applications 'working with' the same master WIF--instead, each application is given its own (copy) of the master WIF and uses that copy. You don't have to do this, but I recommend it.

 

[hanosm]

Thanks! I had a look at some previous posts and modified the shortcuts to run the relevant WIF for each database.

Now I have a problem with different Access versions, so i'm off to write another post!!!