A Run Time connection using a Extractfilename to get the relative path is the way I shall go now. Although design time plugging it all together was really easy and quick to implement.
I did get it working alright even for the installabe version by enforcing the installation path. I was busy with some other problems such as install shield didn't seem to put in all the necessary stuff. Module merges are not error free. Obviously dependencies have to worked out manually in this version of install shield express. Oops I am going off track. I will post on these separately. Thanx Anu Rang, TotallyFreeEnergy http://totallyfreeenergy.freehoxt.com --- In [email protected], Zoran Milenkovic <[EMAIL PROTECTED]> wrote: > > You need to form the connection string at RUN TIME (as per example), not at design time. > > Just note that in my example the "Data" directory is parallel to the Application directory...If you want to have it as a subdirectory, you can use some of the other examples. > > > Anu Rang <[EMAIL PROTECTED]> wrote: If I put in a relative path in the ConnectionString the application > fails to build. It comes up with Unable to locate database file or > something to that effect. I think may be some kind of registry key > with the path entered at the installation time may have to be used. I > just dont know how to do this. Hope I find something on the internet. > > Anu Rang, TotallyFreeEnergy > http://totallyfreeenergy.freehoxt.com > > --- In [email protected], Zoran Milenkovic <deusdino@> > wrote: > > > > If the data is located in the same directory as your EXE file, then > you can remove the path from connection string leaving only the > database name. In that case the application will look for your > database in the current directory. > > > > If you need to have data in separate directory, it should still be > easy to manipulate the connection string, provided that these two > directories are related. > > > > For instance: > > > > const > > cs: String = > > 'Provider=Microsoft.Jet.OLEDB.4.0;'+ > > 'Jet OLEDB:Engine Type=5;'+ > > 'Data Source='; > > > > implementation > > > > ADOConnection1.ConnectionString := cs+'..\Data\MyDataBase.mdb'; > > > > > > Anu Rang <totallyfreeenergy@> wrote: > 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 > > > > > > > > > > > > > > --------------------------------- > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. > Try it now. > > > > [Non-text portions of this message have been removed] > > > > > > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. > > [Non-text portions of this message have been removed] >
