My Access FE will be deployed on a users PC. The BE will be deployed on the users server. I have no idea what directories will be assigned by the user. At this time with limuited resources Installshield is just to expensive unless the Software is deployed to many users (Just testing now). So I have tried using Inno, XP developer and iexpress.
They all have pieces of what I want to do but I don't see how to do it all with one product.
I need to set the table links in the FE to the directory the user sets up for the BE mde which has the Tables.
Also I need to have the installation include access runtime so the app will run no matter what version, if any, the user has installed on their pc.
Right now I can force the installation to be on the pc's C drive and force the directories to load correctly with a known directory name, also on th eC: drivre. But if the user installs on any other drive or installs on a server with a different map letter or does not have a c: drive defined, the app will not run. I do need to have the BE run on a server.
I am thinking that I need to store the chosen directory names in the pc's Registry and when the app first opens ( with a required acceptance of the EULA) then overwrite the TblDefs.Connect names in the FE DB.
I tried overwriting when the app was running and used a db.tbldefs.refresh but that did not work.
I have code in my app which deletes the links and relinks the BE, but it requires a password table which would be on the server and on startup would not be linked.
So, What I need is:
1. a sample script for Inno to add the access runtime.
2. script to add the selected directories to the registry.
3. script in inno to ask the user for a second directory for the BE DB's
4. script to add the BE Directory name to the registry
5. vb code to read the registry entries.
I have code in my app that will unlink and relink the tables.
Also have code that, on startup, checks to see if the tables are loaded.
Auto start runs a macro and I will need to write the code (module) that will check to see if the password table exists and if not then clean out all links and then link the tables to the registry names.
If you have done this or something similar how do you handle it?