Installing a new .MDE with existing .MDW file

[wfweirich]

Our plant uses a QA tracking application that was created and distributed by our division headquarters. The database is written in Access 97. The Db is split with a .MDB as the back-end and a .MDE as the front end. The Db has Users and Groups with all the permissions tied to the groups. The .MDW file is included in the folder structure provided with the application. Recently, division sent out a new version of the .MDE, with instuctions to rename the old one, install the new and use Linked Table Manager to re-link the tables to the back end. This all went well, but when the app was opened up for users to get on, the permissions were gone. Nothing was done to the .MDW file. The only thing that changed was the new .MDE. The app uses a MSACCESS.EXE command along with a /wrkgrp to make sure the correct workgroup information file is used. Can someone explain this to me? Is it possible that a step was ommitted during the installation? Thanks in advance for listening. wfw

 

[SMerrill]

Did Division log into the MDW when they were developing the MDE file?

Division must have a copy of the MDB which they converted and published to you as an MDE file. Furthermore, they must be able to get into their MDB copy as administrators. So ask them to ensure that your MDE works with your MDW.





Take care,
--Shaun Merrill
Seattle, WA

 

[wfweirich]

Thanks for your response. I'm really not sure what the .MDW file that the division developers were signed-on with looks like. My fear is that they did not open the .MDB with the correct .MDW. They may have been using the default (SYSTEM.MDW), completed their application changes, then created the .MDE. This in affect wiped out all the permissions kept in the application .MDW. And , since they did not distribute the .MDB, only the .MDE, we cannot re-create the .MDE with our current version of the application .MDW file. I did do a little testing and verified that the .MDE will carry with it the permissions in place at the time the .MDE is created. Now, you can change them once you have the .MDE open with the desired .MDW file, but, the app will not automatically assume permissions simply because you open the .MDE using a specific .MDW file. The .MDE adopts permissions available at the time the .MDB was open and the .MDE was created. wfw

 

[SMerrill]

Permissions don't get "wiped out". They are simply cumulative. It's rather like a key and a lock. The keys are stored in the MDW and the locks are formed within each MDB explicitly.
The only "adopted" permissions are database owner permissions. You will have to get the Division to re-open the original MDB the way they always have and determine which System.MDW they were using. Bring the production files with you so you can prove to them the production errors they have caused for you.
Hopefully you will talk with someone who understands Jet security inside and out so you don't have to educate them!

Merry Christmas,
~ Shaun