I could really use an explanation of the workgroup information file (WIF in this document). I have read documentation from books and the web and it leaves me with questions. Can anyone help?
The following is the issue that led to my questions:
A couple of days ago my co-worker and I were working on understanding security. Now, my co-worker was the driver of our test and he was not very organized in his approach. So, we were opening and closing different databases and playing with the WIFs not totally understanding what we were doing. Anyway, we changed the security on a database and for some reason he tried to go into an unsecured database (the production database on the lan), or so we thought. When he opened the unsecured database, it prompted him for the security as we had previously set up on earlier databases.
So, there does not seem to be a link from the database to the WIF. If you click on the database file, it uses the WIF that was the last one the user used, regardless of the database the user last opened.
Isn't this poor security. Shouldn't the database be associated with a WIF? The user's open up the mdb file, not a shortcut. How do you associate the WIF with the database when they directly open up the database? If a user wants to bypass security, couldn't he use his default system.mdw and bypass security.
Now there was something about removing the admin user from the database and reassigning all objects to the workgroup administrator. Maybe this solves the problem.
I could sure use an experts analysis on this. If you can spell this out more clearly for me I would really appreciate it.
Thank you in advance for your help.
Tammy
Thank you for your help.
Tammy
The following is the issue that led to my questions:
A couple of days ago my co-worker and I were working on understanding security. Now, my co-worker was the driver of our test and he was not very organized in his approach. So, we were opening and closing different databases and playing with the WIFs not totally understanding what we were doing. Anyway, we changed the security on a database and for some reason he tried to go into an unsecured database (the production database on the lan), or so we thought. When he opened the unsecured database, it prompted him for the security as we had previously set up on earlier databases.
So, there does not seem to be a link from the database to the WIF. If you click on the database file, it uses the WIF that was the last one the user used, regardless of the database the user last opened.
Isn't this poor security. Shouldn't the database be associated with a WIF? The user's open up the mdb file, not a shortcut. How do you associate the WIF with the database when they directly open up the database? If a user wants to bypass security, couldn't he use his default system.mdw and bypass security.
Now there was something about removing the admin user from the database and reassigning all objects to the workgroup administrator. Maybe this solves the problem.
I could sure use an experts analysis on this. If you can spell this out more clearly for me I would really appreciate it.
Thank you in advance for your help.
Tammy
Thank you for your help.
Tammy