VB Application - Package and Deployment Wizard Woes
Posted on 2002-04-30
I've been working on an application. Today, I decided to try and package it into a Setup.exe, a .CAB and Setup.lst files, in order to test the deployment of this "jewel" and see if everything works.
Not all of the stuff works. Mainly, the interaction amongst the different databases (kinda important).
All of these work off of a menu_Click event to load their respective Forms.
I developed this using Visual Basic Pro, Service Pack 5 from within Windows 2000 Professional.
Here are the problems; many seem to be related:
I have a Data Environment object, deSQLAny_1, which was built with a DSN in WIN2K | Control Panel | ODBC. As a standalone .EXE, this ran beautifully (after some work). Now, after being packaged in VB in WIN2K, and deployed within Windows XP Home, I clicked on the menu and I got:
"Run-time error -2147220992 Data Provider could not be initialized." THIS ends my application - down in flames.
Another database example uses the Northwind database. The connection uses the ADODC control with the MS Jet 3.51 OLEDB provider. Standalone - great!
After P&Deploy, I get:
"Provider cannot be found. It may not be properly installed. OK.
"Data Source name not found and no default driver specified." OK
The Form loads, but there is no data to be found.
Another database example uses the ADODC control, this time, connecting to a Personal Oracle8i database. Once again, standalone works great. But after P&D, I get the *longest* message I have ever seen:
"Data Source name not found and no default driver specified. Run-time error -2147467259" Click 'OK'.
"Oracle client and networking components are supplied by Oracle Corporation and are part of the Oracle version 7.3.3 or later client software installation. Provider is unable to function until these components are installed."
I have sample connections to Sybase's SQL AnyWhere databases which don't give me any errors, but they also don't fetch any data either.
I got a second run-time error -2147220992.
I can't remember which one caused that one.
So, it seems to me that I don't have a good present knowledge of dependencies at all (for sure) and how to get these DSNs and /or providers and/or connection strings into this package, this bundle of files. I even have a menu which, when clicked, runs a small PowerBuilder application, connecting to a small (but working) SQL Anywhere database. That ALSO uses a DSN to work. It works fine, by itself and when included into this VB application. Click on it to run after P&D, and the code on the application 'Open' event appropriately works and says, "Unable to Connect to database." OK and it ends right there.
Somehow, there must be a way to include these required DSNs, providers, etc. into this thing.
Once again, I appologize for this being so wordy.
could someone please shove me in the right direction? I've spent a great deal of time on this app and there's more tweaking to be done in design.