I have written using VB6 a fairly complex program which includes database access using ADODC, a DATAGRID and MS Access .db1 files containing several tables.
Connection of the ADODC to the Access database is by CONNECTION STRING. The DATAGRID datasource property is set to ADODC.
For a particular reason I wish to distribute this program other than by using a full-blown Package and Deployment process.
So I have produced a folder containing just the .exe and all the dependency files which the Visual Studio P&D wizard lists when I ask it to generate a Dependency File List.
The program folder thus arrived at is copied to a "foreign" machine, and the .exe is run from that folder.
I have two near-identical "foreign machines". Both, like the source machine, are Win XP Sp3. The difference between them is that that one has VB6 installed and the other does not. (This is so as to test deployment to non-VB6 machines).
For the most part this seems to work OK, but one particular aspect of it - the reading of an Access Database fails when attempting to run the .exe on a NON-VB6 machine. When running the program as described, no errors are displayed but the program fails to open and display the Access .db1 Tables.
However, if I run the selfsame routine on the "foreign machine" which DOES have VB6 loaded, the program runs just fine.
So to investigate this matter further, I wrote a very simple special program. Just a Command button, an ADODC and a Datagrid. On clicking the command button, the ADODC is directed to a (known good) Access .db1 file and table. I made a .exe from this, and tried it on the two "foreign" machines.
Once again, it failed to work on the NON-VB6 machine. No errors were notified, but the Access data table failed to open and the DATAGRID remained unstructured and blank.
However when I ran the .exe on the VB6 INSTALLED machine, it ran fine and the Access table opened correctly into the DATAGRID.
My preliminary conclusion is that although my "deployment package" folder contains both the .exe and all the listed dependency files it must be missing "something" which is nonetheless provided when a "foreign machine" has VB6 installed.
Since I get no reported errors when I run the .exe thus on a non-VB6 machine, what could be missing?
It is appreciated that the deployment method I am trying to use is "unconventional", but there is a reason for this.
Suggestions and ideas welcomed please.
camoore
Wales, UK
Connection of the ADODC to the Access database is by CONNECTION STRING. The DATAGRID datasource property is set to ADODC.
For a particular reason I wish to distribute this program other than by using a full-blown Package and Deployment process.
So I have produced a folder containing just the .exe and all the dependency files which the Visual Studio P&D wizard lists when I ask it to generate a Dependency File List.
The program folder thus arrived at is copied to a "foreign" machine, and the .exe is run from that folder.
I have two near-identical "foreign machines". Both, like the source machine, are Win XP Sp3. The difference between them is that that one has VB6 installed and the other does not. (This is so as to test deployment to non-VB6 machines).
For the most part this seems to work OK, but one particular aspect of it - the reading of an Access Database fails when attempting to run the .exe on a NON-VB6 machine. When running the program as described, no errors are displayed but the program fails to open and display the Access .db1 Tables.
However, if I run the selfsame routine on the "foreign machine" which DOES have VB6 loaded, the program runs just fine.
So to investigate this matter further, I wrote a very simple special program. Just a Command button, an ADODC and a Datagrid. On clicking the command button, the ADODC is directed to a (known good) Access .db1 file and table. I made a .exe from this, and tried it on the two "foreign" machines.
Once again, it failed to work on the NON-VB6 machine. No errors were notified, but the Access data table failed to open and the DATAGRID remained unstructured and blank.
However when I ran the .exe on the VB6 INSTALLED machine, it ran fine and the Access table opened correctly into the DATAGRID.
My preliminary conclusion is that although my "deployment package" folder contains both the .exe and all the listed dependency files it must be missing "something" which is nonetheless provided when a "foreign machine" has VB6 installed.
Since I get no reported errors when I run the .exe thus on a non-VB6 machine, what could be missing?
It is appreciated that the deployment method I am trying to use is "unconventional", but there is a reason for this.
Suggestions and ideas welcomed please.
camoore
Wales, UK