PRB: Cannot Run MS Access 1.x and 2.0 Simultaneously

Article ID: Q120484
Creation Date: 12-SEP-1994
Revision Date: 19-SEP-1996

The information in this article applies to:

Microsoft Access versions 1.0, 1.1, 2.0

SYMPTOMS

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

When you try to start both Microsoft Access version 1.x and Microsoft Access version 2.0 at the same time, you receive two instances of either version 1.x or version 2.0, but not one instance of each version.

CAUSE

Both versions of Microsoft Access use the same executable file name (MSACCESS.EXE). When you have one version of Microsoft Access running and then try to start another version with the same filename, Microsoft Access reruns the version that is already in memory.

RESOLUTION

Give one of the executable files another name. For example, you could rename the version 1.1 MSACCESS.EXE file to ACCESS11.EXE.

Notes:

When you change the name of an executable file, you need to modify the properties of any Windows Program Manager icons that point to that executable file to use the file's new name.
When you want to run both versions at the same time, start the version with the renamed executable file last.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Start Microsoft Access version 2.0.
Using Windows Program Manager, try to start Microsoft Access version 1.1. Another instance of version 2.0 will start.

REFERENCES

For more information about Microsoft Access command lines, search for "command line," and then "Starting Microsoft Access with Command-Line Options" using the Microsoft Access Help menu.

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.