Nic;o
Again your info was right on the mark, the linking tables code and references. I checked and changed some of the references and your code worked great. I now have been testing my latest installation packages on the XP OS and it works on both computers, which is a break through! I found I had to deploy from the XP computer, as my Vista OS would not let me use Program files as a destination.

I know I still have much to...

Nico5038 - I appreciate the follow-up and link to free installer pkgs. After reading further on split databases I understand better the need for your code that you offered. However I do get an error and wonder if I need to add additional code or perhaps it is the need for additional dll's you mentioned. I am not sure how to go about checking for references for other needed dll's but I will look into that next.

Here is the code I wrote...

Nico5038- Thanks for the suggestion. I did relink my db's after moving the files and they are in the same folder. After this is packaged for deployment and installed on someone else's computer, would they need to relink the db's? If so not very user friendly.

The install package works on the XP computer but not on the Vista or Windows7 and I wonder if it has something to do with trusted location and macros.

My app is a MS Access 2007, which I have split into FE and BE (ACCDE and _be.ACCDB). I am using the Package Solution Wizard and have selected to "Require nothing and install the Access 2007 Runtime," providing the source of the AccessRuntime on my computer. If I use a destination folder other than ProgramFiles, I get an error message after installing the app on "some but not all" of my controls.
Error message: "C:\ProgramFile s\Foldername\Da tabaseName_be.a ccdb...