OFFXPDEV: "Invalid Procedure Call or Argument" Error Message When You Package a Database That Has Linked Tables

When you run the Packaging Wizard that is included with Microsoft Office XP Developer, an Access 2002 or an Access 2000 database (.mdb) that has Oracle or AS/400 linked tables or that has Microsoft Exchange data returns the following error message:

To resolve the "Invalid procedure call or argument" error message:

1. In Microsoft Access, remove the linked tables from the database.
2. Compact the database.
3. Start the Packaging Wizard to create a package.
4. After the package is created, open the Support folder within the folder in which the database was packaged. Note that the Support folder contains a copy of the packaged database.
5. Open the database in the Support folder (not the original database), and then re-create the link to the tables.
6. Run the associated BAT file to re-create the CAB file. For example, if the database is Northwind.mdb, run Northwind.bat.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This error does not occur if you create a package that has linked SQL server tables.

Steps to Reproduce the Behavior

1. Create a new database in Access 2002.
2. Use the Microsoft ODBC Driver for Oracle to link a table from Oracle8. The driver is Msorcl32.dll, version 2.573.6526.00.
3. Save the database.
4. Start the Packaging Wizard.
5. Proceed through the wizard by clicking Next until you see the Dependencies page.
6. Click Next. When the wizard searches for additional dependencies, note that you receive the error message that is mentioned in the "Symptoms" section of this article.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For additional information about other causes of the error message described in the "Symtoms" section, click the following article number to view the article in the Microsoft Knowledge Base: