package and deployment wizard

[venugopal]

I have made an project using data reports.For data reports to work u hv to add an data environment which will be connected to the database thru a ole db provider. i an using jet ole db provider. Once i make a setup program thru vb's package and deployment wizard and ship it to client's place everything works but not the data report. The error it pops out is "invalid data source". I think this may be due to the provider i.e microsoft jet ole db provider which is not shipping thru the pavkage and deployment wizard. so if any body knows ay solution please do reply

Venugopal N K
Software Engineer
Orion IT Solutions

[Lothar Haensler]

>I think this may be due to the provider i.e microsoft jet ole db provider which is not shipping thru the pavkage and deployment wizard.
this statement is not true.
the pdwizard includes a file MDAC_TYP.exe that is supposed to install the oledb providers.
your error message doesn't state that the program cannot find the provider. Rather, it says, that the data source is invalid.
That's a different problem.
did you create a DSN?

[venugopal]

Thank you Lothar Haensler for ur reply but i am using the jet ole db provider and it doesn't require any dsn to be created. One more problem is when you create a connection with a dataenvironment the connection object requires a databse name which will take the locl path of my system for eg "C:\project\prj.mdb". but when you install the project on another's system the path which it may install may be "d:\program files\project\prj.mdb". In this case when the report is opened the connection object gets intialized and refers to the path "c:\project\prj.mdb" which is not present. So what is the solution for this.

Venugopal N K
Software Engineer
Orion IT Solutions

[Lothar Haensler]

you can instruct the PDWizard where to store your database. You can define e.g. $(AppPath) as the location for your database.
Then, in your program you can also set the database path to App.Path.
That way you will always access the database from the location where your app is stored.
You can do the same thing during design-time!