Using linked Back End Data Tables in Runtime distribution (URGENT!!) 1

[Guest_imported]

I have my Project split in a Front End Database and the corresponding Data Tables as back-end.
If I use the Package & Deployment Wizard to create a Setup-Package, the paths to the included back-end File are still absolute (e.g. "E:\development\database\project_be.mdb&quot, even if the _be file is included in the Package, it will not be properly linked.
How can I solve this problem without having to force the creation of a specified directory on the costumers machine (like "C:\data&quot.
How can I use relative paths to link Data tables?

 

[MeBeFree]

I realize this original thread is almost a year old but I have the same problem, I want to get the install directory from the registry. Did anyone find a solution to this problem. Please help urgent for me too.

Thanks.

Patti

 

[Stamey]

Use VBA to change the links in the Access front end to reflect the relative path to the DB. I know this can be done with DAO but am not sure how it can be done with ADO.
Let me know if you need code samples. I will try to dig some up.

Chris

 

[throwdini]

I believe there is some sample code in the Northwind Database to refreshlink. It works pretty well and if the tables do not link it opens an "open" dialog box where you can find the datasource and saves the new path to the data.