| Converting secure Access 9x files is a complex process that requires advance planning. Multiuser networked applications are the most common environment for secure Access files. To upgrade either the front-end or back-end .mdb file(s), you must open the files exclusively under an account that has Modify Design or Administer permission for all objects in the .mdb file. Alternatively, you must be the owner (creator) of all the database's objects. All users must close their front-end applications for you to obtain exclusive-open access to the back-end .mdb file. Tip VBA code in secured forms and modules becomes unsecured when converting to Jet 4.0 because the change to the VBA Integrated Design Environment results in a different storage mechanism for your code. After you convert secured front-end .mdbs containing any VBA code, you must use the VBA IDE to password protect the code.
 To review System.mdw basics, see "Jet Workgroup Information Files," p. 153.
For instruction on how to use the Workgroup Administrator tool, see "Establishing Your Own Admins Name, Password, and PID," p. 783.
Upgrading in a Mixed Access 9x and 2000 Environment If you have many database users or several shared databases in operation, it's unlikely that you can upgrade all database users at one time without incurring excessive downtime. In this case, you must perform the following sequence of operations: Make a backup copy of your Access 9x System.mdw file. Launch Access 2003 and choose Tools, Database Utilities, Compact and Repair Database to open the Database to Compact From dialog. Choose Workgroup Files (*.mdw) in the Files of Type list and navigate to and select the shared workgroup file, usually System.mdw, and compact it with the same name. Click Cancel to close the Convert/Open Database dialog. Open the Access 97 version of the front-end .mdb file in Access 97 to verify that the compacted System.mdw file opens with your Admins account, and you have design permissions for front-end objects. Verify that members of groups other than Admins don't have design permissions. Choose Tools, Security, Workgroup Administrator, and join the workgroup you updated in step 2. Close and reopen Access 2002. Open and convert the secure front-end .mdb file to Access 2000 format. Thoroughly test the Jet 4.0 version of the secure application .mdb file with the existing Access 97 data .mdb file(s) and the compacted Access 97 System.mdw file. Convert and distribute the upgraded front-end .mdb file to users.
Upgrading the Back-End Database and Workgroup File After you've upgraded all your client .mdbs, you can upgrade the back-end (data) .mdb file, if you have a compelling reason to do so. If you decide to upgrade the back-end database and optionally the workgroup file, complete the upgrade process as follows: Compact the shared data .mdb file with a new name so that you can convert the file to a new version with the same name as the old version. Upgrade the data .mdb file to Jet 4.0. Caution Don't delete the original .mdb file. You might need to revert to the original files in case you encounter conversion problems. Create a local copy of the existing shared workgroup file and join the local workgroup so you can compact the original workgroup file. Compact the shared workgroup file with a new name and then convert it to Jet 4.0 with the original name. Caution Don't delete the original .mdw file. You might need it as conversion insurance. After testing the new configuration, request each user to open Workgroup Administrator and rejoin the workgroup with the new workgroup file.
|
