Microsoft KB Archive/230468

= MOD2000: Some Data Access Files Cause "Missing Dependency Information" Dialog Box to Open During Package and Deployment Wizard =

Article ID: 230468

Article Last Modified on 7/30/2001

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q230468



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



SYMPTOMS
When you run the "Package and Deployment" Wizard to package a solution, the Missing Dependency Information dialog box opens with a list of files that do not have dependency information. This occurs even though your Visual Basic for Applications project includes only references to standard Microsoft data access components.



CAUSE
You have included references in your Visual Basic for Applications project for technologies included in the Microsoft Data Access Components (MDAC). The technologies and files included in MDAC are not designed to be distributed alone, so some of the files do not have dependency files. The MDAC files known to cause this dialog box to appear are:

NOTE: If you do not want the "Package and Deployment" Wizard to check for dependency files for these specific files in the future, you can click to select the check box next to the files in the dialog box, and then click OK.



RESOLUTION
When you receive the Missing Dependency Information dialog box in reference to the files listed in the "Cause" section of this article, you can click OK to bypass the dialog box.

To ensure that all files required for using MDAC technologies are present on the computer on which you are going to install your solution, be sure to distribute the entire MDAC package. You can distribute the MDAC package by manually including the MDAC installation file, MDAC_typ.exe. The default location of MDAC_typ.exe is C:\Program Files\Microsoft Office\ODETools\V9\PDWizard\Redist.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Office 2000 Developer, "Package and Deployment" Wizard.



MORE INFORMATION
When you used the "Package and Deployment" Wizard to package a solution for distribution, the wizard creates a list of files that need to be included in the distribution package for your application to work after it is installed. After creating the file list, the "Package and Deployment" Wizard searches for dependency files for each of the files that you include in your application package. A dependency file is named identically to the file it is related to, but uses the *.dep extension.

A dependency contains a list of additional files and other information that ensure the proper functioning of its associated file. The use of dependency files ensures that when your application is installed on the target computer, all of the files that are required to run your solution will be installed on the computer.

When you use the Data Connectivity functionality provided by the Microsoft Data Access Components, deploy the entire MDAC 2.1 installation program, MDAC_typ.exe, with your solution. This ensures that all of the required dependencies for these technologies are installed on the target computer. The following is a list of functionality provided by MDAC 2.1.

ActiveX Data Objects 2.1 (ADO)

ActiveX Data Objects (multi-dimensional) 1.0

ADO Ext. 2.1 for DDL and Security

Jet and Replication Objects 2.1

Jet 4.0

Jet ODBC

ODBC

OLEDB

Oracle ODBC

Oracle OLEDB

Remote Data Services (RDS)

SQL Server ODBC

SQL Server OLEDB

Visual FoxPro ODBC

NOTE: Not all of these technologies are checkable options in the References dialog box. They are used either in support of another technology or through a different interface, such as the ODBC Administrator.

Additional query words: pra

Keywords: kbbug kbnofix kbpdwizard kbappsetup kbwizard KB230468

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.