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
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