> sorry, I don't undestand about what "Using the "-o" switch on the command
> line"
> you talk : a command line of the application installer(Inno etc.) or a
> Paradox - command line.
I'm talking about the command line that starts your application.
If you search the Paradox help for "Command-line" you will get the full
listing of the different options.
What I have done is to create a BDE configuration file that includes all the
settings I need for my application. I then supply that config-file together
with my application and make sure that the application is started with a
shortcut that include the -o pointing to my config file.
Here is one example from this computer:
"C:\Program Files (x86)\Corel\WordPerfect Office
2002\Programs\pdxwin32.exe" -c -q -p E:\Databas\PdoxPriv\Test -o
E:\Databas\CFG\ANSI.CFG -w E:\Databas\App\Test Start.ssl
I agree with Leslie that there is a problem with a custom config-file as
Paradox will not allow you to run separate session with different config
files in use. In my case that is not a real problem.
I really don't want to mess with the default settings of the BDE. What if
the user have another application that uses the BDE? If that application
expects a certain number format, date format och language driver it could
cause a lot of problem. What if the user change the BDE settings after the
install? For me the "-o" seems to be the most reliable way to ensure that my
settings are in use for my application.
The reason why I never have used Leslies BDE-installer is that I prefer to
do as little as possible. With "my" approach I can use the default
installation of the BDE that comes with P10 runtime which is very convenient
as I don't use a professional installer for my applications (I use a simple
BAT-file).
We are all working in different environments and I don't claim my method to
be optimal, but it works for me and it seems like it could work for you as
well.
Anders