You can build the connection string in code, based on a path chosen in a file dialog.
You can build a default path using the application path (from the application object at runtime) and add to it your default relative path. Then the program can look for the mdb, and not finding it, prompt the user to tell where they might have left it. If you think the app will ever be used in Vista, you won't be able to store the mdb in the program folder, so you might as well get used to allowing the mdb to be anywhere. There are some very specific folders defined by MS where they'd really like you to put data. Jeremy -----Original Message----- From: advanced_delphi@yahoogroups.com on behalf of Anu Rang Sent: Wed 4/30/2008 6:55 AM To: advanced_delphi@yahoogroups.com Subject: [advanced_delphi] Deployment of a Access DB based application using InstallShield Express Hi, Having built my application using a local Access database, I was trying to deploy my application using Installshield express. The thing about deployment on target computer is that normally where the application is installed is decided by the user. Ofcourse it is possible to enforce a particular directory path for installation. Still it is tricky to get a relative path mapped in the ADOConnection object. I just used use connection string and built it using the ADOConnection wizard. If anyone has more info or knowledge I would really appreciate it since this path to the .mdb file really has to be relative and not hard coded. Anu Rang, TotallyFreeEnergy http://totallyfreeenergy.freehoxt.com
<<winmail.dat>>
