Linked Tables in deployment setup

[Orcanut]

How can I setup a table linkage for deployment when I do not know to which drive the client will install the application?

e.g. Initially the linkage is to a backend on drive C:
If I run the deployment package and install to a different drive however the linkage is broken and if it is a "runtime" application I cannot re-establish the link.

Thanks for your thoughts.

Jim Baird

 

[danvlas]

Check thread705-345743

Dan

 

[VBslammer]

If you're deploying a runtime app this is probably the most important feature you have to create, since the built-in Linked-table manager is disabled.

In my apps, I use Installshield to deploy the program and provide a form that allows the end-user to define the back-end path during installation, which is written to the registry. When the program launches, it checks the table links and if it finds them broken, it checks the registry key to see if there is an entry (new installation). If so, the re-linking code runs to re-establish the links automatically - without user intervention.

If the registry path is invalid, then I show a form with a commondialog control on it so the user can locate the backend and click the 'Relink' button. Most of the code to relink tables is provided in the MSDN library.

I developed a class module that handles all my relinking chores, however it is copyrighted by my client and I can't share it without penalty.

I also used a cloned Linked-Table manager form in one of my apps (looks identical to the built-in form) and added a menu for it so the user could bring it up and manage the links.

My current app just uses a custom menu bar with a File->Open command to launch the table-linker common dialog form.

The instructions for re-linking your back-end are provided by Microsoft in Article ID: Q181076

Good Luck,

VBSlammer

 

[Orcanut]

Thanks Dan, Slammer

Jim