ACC: Could Not Find SYSTEM.MDA or UTILITY.MDA File

Last reviewed: May 7, 1997
Article ID: Q90105

The information in this article applies to:

Microsoft Access versions 1.0, 1.1, and 2.0

SUMMARY

Novice: Requires knowledge of the user interface on single-user computers.

When you start Microsoft Access, you may receive one or both of the following error messages:

   Couldn't find file 'SYSTEM.MDA' (version 1.x)
   Couldn't find file '<path>\SYSTEM.MDA' (version 2.0)

   Couldn't find file 'UTILITY.MDA' (version 1.x)
   Couldn't find file '<path>\UTILITY.MDA' (version 2.0)

These errors occur if the SystemDB and UtilityDB settings in the [Options] section of the MSACCESS.INI file in version 1.x, or the MSACC20.INI file in version 2.0, point to a directory that does not contain the SYSTEM.MDA or UTILITY.MDA file. These errors also occur if the directory points to a share to which there is no connection.

If the directory does not exist, you receive the following error message:

   Invalid Path '<pathname>' (version 1.0)
   '<pathname>' isn't a valid path (versions 1.1 and 2.0)

MORE INFORMATION

A good way to manage the MSACCESS.INI or MSACC20.INI file is to keep backup copies that pertain to particular setups. Have one set up for starting in a workgroup on a network and have another that allows for starting on a local machine. To change setups, copy the appropriate backup .INI file over the MSACCESS.INI or MSACC20.INI file.

Keywords : kberrmsg kbsetup StpOthr
Version : 1.0 1.1 2.0
Platform : WINDOWS
Hardware : x86
Issue type : kbinfo

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.