PRA: Setup Wizard Cannot Use Files with Same Names

Article ID: Q124283
Creation Date: 27-DEC-1994
Revision Date: 05-FEB-1996

The information in this article applies to:

Microsoft Access Developer's Toolkit version 2.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you use the Setup Wizard to create Setup disks for your custom application, if you include two or more files whose names differ only by the last character in the three-letter extension, only one of the files is installed.

CAUSE

When the Setup Wizard compresses files to create the Setup disks, it removes the last character of each file's three-letter extension and replaces it with an underscore character. The filenames MYAPP.MDB and MYAPP.MDA, for example, would both be compressed to MYAPP.MD_.

RESOLUTION

There are three ways to work around this problem.

Method 1

Rename the files that differ only by the last character of the three-letter extension so that they differ by at least one more character.

Method 2

Use the Network Setup (Flat) option to create a single directory with uncompressed files. This option will not fit all the files on disks, but is practical if you are creating a Setup to be run from a CD-ROM or from a network file server.

Method 3

NOTE: This method involves modifying the SETUP.INF file and is not supported by Microsoft Product Support Services. You should use this method only if you cannot use either of the first two methods.

This method involved modifying the SETUP.INF file to rename files after they have been installed. The following steps demonstrate this method:

Run the Setup Wizard as usual to create the Setup disks.

Make a backup copy of the SETUP.INF file located on Disk 1.

Open the SETUP.INF file in any text editor (such as Windows Notepad). Locate the [Default File Settings] section of the file and then change the line that reads
```
      "STF_ROOT" = "ROOT"
```
to read:
```
      "STF_ROOT" = ""
```
Locate the [User Files] section of the file and then locate the name of the file that you want to rename.

Change the entry in position 12 on the appropriate line to the new file name. This entry is usually empty. For example, you would change

      [User Files]
      "myapp_mdb"= 1,myapp.mdb,,,,,,,ALWAYS,,,,,,,65536,,,,,
      "myapp_mda"= 1,myapp.mda,,,,,,,ALWAYS,,,,,,,65536,,,,,

      (These settings will lose the second file.)

to be:

      [User Files]
      "myapp_mdb"= 1,myapp.mdb,,,,,,,ALWAYS,,,,,,,65536,,,,,
      "myapp_mda"= 1,myapp.mda,,,,,,,ALWAYS,,,myapp.mda,,,,65536,,,,,

      (These settings will retain the second file.)

Save and then close the SETUP.INF file.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft Access Developer's Toolkit version 2.0. This problem no longer occurs in the Microsoft Access Developer's Toolkit version 7.0.

MORE INFORMATION

Steps to Reproduce Problem

Create two text files called README.TXT and README.TXZ.
Run the Setup Wizard and include both the text files. Create 1.2 MB or 1.44 MB distribution disks.
Run Setup from the disks you created in step 2. Note that only one of the two files you included is installed in the application directory.

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.