Access 2003 VBA Programmer's Reference

A.4. Converting a Secured Database

This section will cover issues associated with converting a secured database to Access 2003. To really delve into security issues please read Chapter 16, which provides detailed information about creating and working with workgroup information files (WIFs).

As previously mentioned, converting a secured database entails a few extra steps and considerations. For one thing, you will need to have the necessary permissions to convert the database. Plus, there is a WIF to deal with. Ideally, if all users have converted to 2000, 2002, or 2003, the WIF should be recreated to take advantage of the new security and performance features. Do not create a new WIF if some users still have pre-2000 versions of the application. You do not need to recreate an Access 2000 MDW. And, you don't need to worry about security with an Access project, because its security is maintained in the associated 11.

When upgrading a secured database from Access 95 or 97 to 2003, recreating the WIF in the new format is beneficial but it is not mandatory. However, the MDW should at least be compacted after the database is converted. After the MDW is compacted, users will need to use the Workgroup Administrator to join that MDW before opening the converted database.

A.4.1. Converting a Secured Database from Access 95 or Later to Access 2003

When Access 2003 is installed, it creates a new WIF. This becomes the default WIF for Access 2003. However, to convert a secured database, you ...