Unanswered: Deploying split database to different places/different paths
I am working on an application that will ultimately be deployed into multi-user situations in 4 separate offices -- i.e., each office will have their own data. I think I have finally convinced the powers that be that we should split our application into a front end interface and back end data. But, I'm not sure how I go about deploying this when I don't know where the files will be installed at each location (i.e., I will not be to require that a specific directory is used).
Anything from general approach to sample code would be suggested. I hate to ask such an open-ended question, but I'm feeling stumped.
I have an auto-connection thing going on -- when the database first opens, it attempts to open one of it's linked tables. If it fails, then it prompts for the back end location and once specified, re-links all the tables.