Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Package & Deploy with Jet4 mdb

Status
Not open for further replies.

DK47

Programmer
Jun 3, 2003
118
US
I have had some bad luck installing my vb6 programs that use local databases created by Jet4 on user machines.

Looking through the faqs on this site I have not found a reasonable answer to these troubles.

The following are my concerns and questions:
1. When the programmer creates a new Jet4 mdb via the Visual Data Manager where should the file be created and saved so that when the program is deployed on another machine the path written into the ado's connection will be a valid one on the user's computer?
I have tried creating the mdb and saving it in the folder where the project was being developed. But when the project is deployed on the user's pc I still got a "path to mdb not found" message!!!

2. When vb6 deploys, it creates the project, by default, in the C:\Program Files\Program1 directory. With the program running there, how is a path connection written into the ado supposed to find the mdb?

3. Is there a way to change the settings during the packaging of the project so the program will install on the user's computer at a location specified by the programmer?

4. Should the mdb file be present in the Support folder after the cab file has been opened?

5. Will vb6 include the mdb file in the package using the Package and Deploy Wizard or will it have to be added manually?

Any help is greatly needed.
Thanks
Dwight
 
First I would recommend using the Visual Studio Installer - it gives you much greater control over what happens during deployment. You can download it free from Microsoft's website.

1. When using the P&DW add the mdb, but tell it to write it to the app directory, and in your code specify the app directory for the mdb.

2. See above

3. I don't think so.

4. If you've added it as per (1), it should be there.

5. You'll need to add it manually.

But really, use VSI! You can control where shortcuts, etc get placed, install directory, and all that sort of thing.

Andy
"Logic is invincible because in order to combat logic it is necessary to use logic." -- Pierre Boutroux
"A computer program does what you tell it to do, not what you want it to do." -- Greer's Third Law
 
Oh and don't forget to include MDAC_TYP (Microsoft Data Access Components) as well, in case the target PC doesn't have it installed. Also downloadable free from MS.

Andy
"Logic is invincible because in order to combat logic it is necessary to use logic." -- Pierre Boutroux
"A computer program does what you tell it to do, not what you want it to do." -- Greer's Third Law
 
Andy
Thanks again buddy.

I'll get VSI.

Yest I know about MDAC_TYP as well as the dcom98.exe file for 95 & 98 users.

A yourself a great night Andy.

Dwight
 
Why, thank you. You too, Dwight.

Andy
"Logic is invincible because in order to combat logic it is necessary to use logic." -- Pierre Boutroux
"A computer program does what you tell it to do, not what you want it to do." -- Greer's Third Law
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top