This article was previously published under Q231923
This article has been archived. It is offered "as is" and will no longer be updated.
This article shows how to package and distribute MSDE for Visual Studio using the Package and Deployment Wizard (PDW) tool that ships with Visual Basic 6.0. There are two main steps to perform:
Create a Standard Setup Package that redistributes necessary MSDE files to target machines along with your Visual Basic application. The MSDE files will be used on target machines to set up MSDE. This could be done in two ways with the PDW:
MSDE manual setup
MSDE automatic setup via a Window's Program group icon
Use a custom database with MSDE on the target machine.
The following procedure assumes that you have downloaded the MSDE for Visual Studio redistribution package (Msdex86_pkg.exe) and have extracted the redistribution file (Msdex86.exe). The MSDE for Visual Studio CD also has the redistribution files in the MSDE folder.
Step 1: Create the Redistribution Package
In this approach, MSDE setup must be launched manually after redistributing MSDE files to the target machine. This can be accomplishedfrom either the MS-DOS command line or from the Start/Run menu.
On the original development machine, start the Package and Deployment Wizard. Choose a Visual Basic project and click the Package icon.
In the Package and Deployment Wizard - Package Type dialog box, click Standard Setup Package.
Click Next; leave the default settings.
Click Next. In the Package and Deployment Wizard - Included Files dialog box, click Add. Include the following files within the setup wizard:
Any custom database (.mdf file) that needs to be used with MSDE on the target machine
Click Next. In the Package and Deployment Wizard - Cab Options dialog box, choose one of the following two options:
Single Cab: This option is useful when distributing the Package on a large media such as a CD-ROM. This option packages all of the files into a single CAB file.
Multiple Cab: This option is useful when distributing the package on disks. Choosing this option packages the files into multiple CAB files.
Click Next. In the Package and Deployment Wizard - Installation Title dialog box, choose a setup screen title.
Continue through the wizard, selecting the default settings, until you reach the Package and Deployment Wizard - Shared Files dialog box. In this dialog box, mark the components you want shared.
Continue through the wizard; click Finish. The package is now complete and can be installed onto target machines.
Run the setup program on the target machine.
From the Start menu, point to Run (or from the MS-DOS command prompt), type the following, AppPath\msdex86.exe -s -a -f1 "AppPath\unattend.iss" where AppPath is the application directory specified by the user, or the default directory specified in the Setup section. This launches the MSDE setup program.
Automatic Setup via Window's Program Group
This allows the creation of a program group that appears under the Start/Programs menu on Window's desktop. Once clicked, this program group automatically launches the MSDE setup process on the target machine.
On the original development machine, start the Package and Deployment Wizard and repeat steps 1 through 6 in the "Manual Setup" process above.
In the Package and Deployment Wizard - Start Menu Items dialog box, click New Item. Then, do the following:
In the Name box, type Start MSDE Setup.
In the Target box, type the following:
msdex86.exe -s -a -f1 "$(AppPath)\unattend.iss"
In the Start In box, leave the default macro: $(AppPath).
Repeat steps 7 and 8 above. The package is now complete and can be installed onto target machines.
Step 2: Using a Custom Database with MSDE
When MSDE setup is completed successfully on target machines, only the following databases will be available with MSDE:
Once you have redistributed the custom database (.mdf) file onto the target machine as shown in step 4 of the "Manual Setup" section above, you can then apply any of the following approaches:
Run the stored procedure "sp_attach_db" to attach your database to MSDE as follows: