Article ID: 241479
Article Last Modified on 7/30/2001
APPLIES TO
- Microsoft Office 2000 Developer Edition
This article was previously published under Q241479
Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
When you use the Package and Deployment Wizard in Microsoft Office 2000 Developer, you see no specific option to include a Workgroup Information file.
CAUSE
In Microsoft Office 2000 Developer, you can still specify a custom Workgroup Information file in the Package and Deployment wizard, but not in the same way that you did in the Setup Wizard in Microsoft Office 97 Developer Edition. This is because the Package and Deployment Wizard is now designed for use with all Office products and is not Access-specific.
RESOLUTION
In the Package and Deployment Wizard, you can specify the custom Workgroup Information file through the Start Menu Items page. You can modify the target file command-line string and use macros that are resolved by the Package and Deployment Wizard Setup file, Setup1.exe. For example:
You specify the following as the shortcut:
/wrkgrp "$(AppPath)\System.mdw" "$(AppPath)\Northwind.mdb"
When this is installed, a shortcut is created that has the following command line:
C:\Program Files\Office\MSACCESS.EXE /wrkgrp "C:\Program Files\Northwind\System.mdw" "C:\Program Files\Northwind\Northwind.mdb"
For additional information about Access command line switches, click the article number below to view the article in the Microsoft Knowledge Base:
209207 ACC2000: How to Use Command-Line Switches in Microsoft Access
NOTE: Make sure to also include the custom Workgroup Information file on the Package and Deployment Wizard - Included Files page.
MORE INFORMATION
CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.
The following is a step-by-step example of how to specify a custom Workgroup Information file:
- In Windows Explorer, find your System.mdw file. The default location is \Program Files\Microsoft Office\Office.
- Highlight System.mdw to select it, and then on the Edit menu, click Copy.
- On the Edit menu, click Paste.
- Right-click the Copy of System.mdw file, and then rename it to Test1.mdw.
- Open the sample database Northwind.mdb.
- Press ALT+F11 to open the Visual Basic Editor.
- On the Add-ins menu, if the Package and Deployment Wizard is listed, skip to step 11.
- On the Add-ins menu, click Add-in Manager.
- In the Available Add-ins list, click VBA Package and Deployment Wizard.
- Under Load Behavior, click to select the Loaded/Unloaded check box, and then click OK.
- On the Add-ins menu, click Package and Deployment Wizard.
- On the first page of the Package and Deployment Wizard, click Package.
- Click Next and accept the defaults until you see the Package and Deployment Wizard - Included Files page.
- Make sure the Include Access Runtime check box is selected to ensure that the Access Run Time component will be installed if users do not have a copy of Access on their computer.
- Click Add, and then add the Test1.mdw file that you created earlier.
- Continue to click Next until you see the Package and Deployment Wizard - Start Menu Items page. In the tree structure under Start menu items, note the Northwind group, and under that, the shortcut for Northwind.
- Click the Northwind shortcut, and then click Properties.
- In the Start Menu Item Properties dialog box, under Target, type the following:
/runtime /wrkgrp "$(AppPath)\Test1.mdw" "$(AppPath)\Northwind.mdb"
- Click OK, and then click Next to move to the Package and Deployment Wizard - Install Locations page.
- Make sure that the Installation Location cell for the Test1.mdw file is set to $(AppPath). To do so, click in the cell, click the arrow that appears, and then click $(AppPath) in the list.
- Continue to click Next until you reach the end of the wizard, and then click Finish.
Now when you install the resulting application, Northwind.mdb will run with a specific workgroup information file, Test1.mdw, which is in the folder specified for the application.
For additional information about how to use the Package and Deployment Wizard macros in custom command lines, click the article number below to view the article in the Microsoft Knowledge Base:
236519 MOD2000: How to Use Macros and Switches for Shortcuts in the Package and Deployment Wizard
Additional query words: pra prb runtime wrkgadm add doesn t does not
Keywords: kbnofix kbpdwizard kbprb KB241479
