Article ID: 159411 - View products that this article applies to.
This article was previously published under Q159411
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
During the installation of a Visual Basic application that uses Jet, a message box entitled "APPNAME Setup" appears with the following error message:
Invalid line in setup information file!
NOTE: The file name, date, version number, and size shown in the error message may vary according to the build of Jet being distributed.
The 32-bit Jet components are registered as installed to a network server with a UNC path. The error message appears because this registration occurs before you install your Visual Basic application.
NOTE: Microsoft Developer Support does not support the modification of the setup process or any of the setup files. Support is provided for the Setup Wizard only on an "as is" basis.
Several workarounds are possible. The following three are recommended:
The Setup1 project routines that check the validity of the installation paths will mark UNC paths as invalid. UNC paths for DAO frequently occur on systems where you install Office95 from a network server that uses UNC paths, and select the option to leave system components on the network.
Article ID: 159411 - Last Review: February 24, 2014 - Revision: 2.0