MOD2000: Cannot Specify Custom Install Locations in "Package and Deployment" Wizard

ID: Q236471

The information in this article applies to:

Microsoft Office 2000 Developer

Advanced: Requires expert coding, interoperability, and multiuser skills.

SYMPTOMS

In the "Package and Deployment" wizard, in the step titled "Install Locations," you cannot type a custom install location for any of the components.

CAUSE

Many predefined install locations are available from the list in the Install Location field (see the "More Information" section); however, you cannot type characters in the field.

MORE INFORMATION

You are limited to the paths that you can choose from the list available in the Install Location field. The list contains macro names that represent specific paths. The macros are as follows:

Macro Name Description

$(AppPath) Folder to which the run-time application is installed

$(ProgramFiles) Folder to which applications are usually installed

$(CommonFiles) Common folder to which shared files are sometimes installed

$(CommonFilesSys) The System folder located in the Common Files folder

$(Font) The location of fonts on the computer

$(MSDAOPath) Location that is stored in the registry for Data Access Objects (DAO) components (You should not use this for your files.)

$(OfficeAddInPath) The location of Office add-ins

$(WinPath) Where Windows or Windows NT are installed

$(WinSysPath) The system folder under the Windows or Winnt folders

Additional query words: prb

Keywords : kbdta modPDWizard
Version : :
Platform : WINDOWS
Issue type : kbprb