Article ID: 266769 - Last Review: January 26, 2005 - Revision: 3.1 ACC2000: Error Starting Microsoft Access with Custom ProfileThis article was previously published under Q266769 Advanced: Requires expert coding, interoperability, and multiuser
skills. This article applies only to a Microsoft Access database (.mdb). Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows Registry On This PageSYMPTOMS When you start Microsoft Access 2000 or a run-time
application with a custom profile, you receive the following error message:
An error occurred and this feature is no longer
functioning properly. Would you like to repair this feature now? Microsoft Access couldn't find file 'system.mdw'. This file is required for
startup. CAUSE Microsoft Access is unable to locate a workgroup file
(System.mdw) during startup. This occurs when all of the following conditions
are true:
RESOLUTION Either use the /Wrkgrp switch in the shortcut to point to a workgroup file or include a
Jet subkey in the custom profile that points to a workgroup file.
Note You must also make sure that the Everyone and the TERMINAL SERVER USER groups have full permission on the HKEY_CLASSES_ROOT\TypeLib\{4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}\9.0 registry key. To do so, follow these steps: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Use the /Wrkgrp Switch to Specify a Workgroup FileThe easiest approach to resolve the problem is to include a /Wrkgrp switch in the shortcut that points to a valid workgroup file. For example, create a shortcut on the desktop with the following command-line.NOTE: The paths to Msaccess.exe and the System.mdw file may be different on your computer. Make sure the paths in your shortcut accurately reflect the location of Msaccess.exe and System.mdw on your computer. "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /Wrkgrp "C:\MyApplication\System.mdw" /Profile Test 209207
(http://support.microsoft.com/kb/209207/EN-US/
)
ACC2000: How to Use Command-Line Switches in Microsoft Access
For
additional information about writing macros and switches for shortcuts in the
Package and Deploy Wizard, click the article number below to view the article
in the Microsoft Knowledge Base: 236519
(http://support.microsoft.com/kb/236519/EN-US/
)
MOD2000: How to Write Macros and Switches for Shortcuts in the Package and Deployment Wizard
Include a Jet Subkey in Your Custom ProfileWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To create a Jet subkey in your custom profile to specify the path to the workgroup file, follow these steps:
STATUS This behavior is by design. MORE INFORMATION When you open a database (.mdb) file in Microsoft Access,
the Jet database engine requires a workgroup file (System.mdw) in order to
start. To determine the path to the workgroup file to use, Microsoft Access
goes through several steps. If the shortcut contains a /Wrkgrp switch that points to a valid workgroup file, Microsoft Access uses that workgroup file. If the shortcut does not contain a /Wrkgrp switch, Microsoft Access searches the Windows registry and uses the location specified in the Jet subkey of the profile in use. When you use a custom profile to start your application, Microsoft Access does not use the default Access profile found at HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Access when it starts. Instead, it uses the subkeys of the custom profile that you created. If the profile does not contain a Jet subkey with the path to the workgroup file, Microsoft Access searches the folder where Msaccess.exe is located (for example, C:\Program Files\Microsoft Office\Office). If Microsoft Access still cannot locate a workgroup file, it returns the errors that are mentioned in the "Symptoms" section of this article. This issue is more likely to occur on computers where Microsoft Access 2000 SR-1 was installed from CD, instead of on computers that were upgraded to SR-1. This is because the default location for the workgroup file (System.mdw) changed in SR-1 and is not in one of the paths mentioned earlier. Therefore, if you use a custom profile to start Microsoft Access 2000 SR-1 on a computer and do not include the /Wrkgrp switch, you will receive the errors that are mentioned in the "Symptoms" section of this article. Creating a Custom Profile to Use with Microsoft AccessThe following steps demonstrate how to create a custom profile to use with Microsoft Access. This example uses the TitleBar string value in the custom profile to customize the titlebar of the application window when Microsoft Access starts.
Steps to Reproduce the Behavior
REFERENCES For more information about using custom profiles, click Microsoft Access Help on the Help menu, type custom profiles in the Office
Assistant or the Answer Wizard, and then click Search to view "Customize your application's environment with Microsoft Access user profiles."
| Article Translations
|
Back to the top
