HOWTO: Redistribute MSDE Using the Package and Deployment Wizard

• Microsoft Data Engine (MSDE), version 1.0
• Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 6.0

SUMMARY

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:

1. Step 1: 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.
   
   
   



2. Step 2: Use a custom database with MSDE on the target machine.

MORE INFORMATION

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

Manual Setup

1. On the original development machine, start the Package and Deployment Wizard. Choose a VB project and click the Package icon.



2. In the Package and Deployment Wizard - Package Type dialog box, click Standard Setup Package.



3. Click Next; leave the default settings.



4. Click Next. In the Package and Deployment Wizard - Included Files dialog box, click Add. Include the following files within the setup wizard:
   
   
   • Readme.txt
   
   
   
   • Msdex86.exe
   
   
   
   • Unattend.iss
   
   
   
   • License.txt
   
   
   
   • Any custom database (.mdf file) that needs to be used with MSDE on the target machine
   
   
   



5. 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.
   
   
   



6. Click Next. In the Package and Deployment Wizard - Installation Title dialog box, choose a setup screen title.



7. 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.



8. Continue through the wizard; click Finish. The package is now complete and can be installed onto target machines.



9. Run the setup program on the target machine.



10. 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

1. On the original development machine, start the Package and Deployment Wizard and repeat steps 1 to 6 in the "Manual Setup" process above.



2. In the Package and Deployment Wizard - Start Menu Items dialog box, click New Item. Then, do the following:
   
   
   1. In the Name box, type Start MSDE Setup.
   
   
   
   2. In the Target box, type the following:
      
      msdex86.exe -s -a -f1 "$(AppPath)\unattend.iss"
   
   
   
   3. In the Start In box, leave the default macro: $(AppPath).
   
   
   



3. Repeat steps 7-8 above. The package is now complete and can be installed onto target machines.

Step 2: Using a Custom Database with MSDE

• master



• model



• msdb



• tempdb

• Run the stored procedure "sp_attach_db" to attach your database to MSDE as follows:

  
  EXEC sp_attach_db @dbname = N'dbname', @filename = N'filepath\filename.mdf'
  	
  EXEC sp_attach_db 'Test', 'c:\Mssql7\Data\Test.mdf' 




• Use the Microsoft OLEDB Provider for SQL Server to attach the .mdf database file and connect to the database directly. In this case, the connection string should resemble the following:

  
  "Provider = SQLOLEDB.1; User ID = your_user_id; Password = your_password;Initial Catalog = db_name; Data Source = server_name;
  Initial File Name = db_file_path\db_file_name.mdf" 




• Use the Microsoft OLEDB Provider for SQL Server to point to the local MSDE. In this case, the connection string should resemble the following:

  
  "Provider = SQLOLEDB.1; User ID = your_user_id; Password = your_password;
   Initial Catalog = db_name; Data Source = (local)" 




• Use the Microsoft OLEDB Provider for ODBC drivers (MSDASQL) to connect to MSDE. You can create a DSN on each target machine or use a DSN-less connection
  
  NOTE: The third and fourth approaches above require attaching the database prior to using the connection string(s).



• You can optionally use SQL-DMO to start MSDE, attach or/and detach your custom database to MSDE.

REFERENCES

• Resources for developers building applications with MSDE, including whitepapers, general additional FAQS, and sample code can be found at:

  http://msdn.microsoft.com/vstudio/msde




• For additional information on the process of installing a user-database on MSDE, please see the the following article in the Microsoft Knowledge Base:
  
  

  Q224071 INF: Moving SQL Server 7.0 Databases to a New Location




• For additional information on the Package and Deployment Wizard, please refer to the Visual Basic documentation.

© Microsoft Corporation 1999, All Rights Reserved.
Contributions by Ammar Abuthuraya, Microsoft Corporation

Additional query words:

Keywords          : kbDatabase kbGrpVBDB kbMSDE100 
Version           : WINDOWS:1.0,6.0
Platform          : WINDOWS 
Issue type        : kbhowto 

Last Reviewed: June 2, 1999