|Subject:||Re: BDE Installer
|Date:||Mon, 26 Aug 2013 17:29:12 +1000
|From:||"Leslie Milburn" <CDB4W@NOSPAM.bigpond.com>
"Anders Jonsson" <anders.jonssonREMOVE@THISorrspelet.se> wrote in message
> I have no clue why Leslies installer doesn't work with your setting for
> thousand separator. I don't use his installer. I always install the BDE
> that come with P10 runtime and never change any BDE-settings on the client
When I get a minute I will have a look why this particular flag has a
problem, its been a while.
Ok, so I took a look at the code and there is a spelling mistake in there as
well with the additional 'S' for this particular setting so it never gets
I will take a look at making this change on the weekend and upload an
update. Good spot !!
> With Windows Vista, 7 and 8, I don't rely on the settings I see in the
> BDE-administrator is actually in use.
> Using the "-o" switch on the command line has been 100% reliable for me.
This approach also has its issues such as causing a "Multiple config
files in use" error when multiple BDE applications are running. My
application runs in an environment where there are quite a few BDE
applications so its a big issue for me. The -o switch was not a problem for
the 16 bit IDAPI but since it went 32 bit, really it should not be used.
The correct method (and the last documented by borland way back) to change
the BDE settings (where possible) is actually to do them in code at runtime
in a manner that affects the current session only. This means using the BDE
API (and as stated in the past not directly modifying the registry, but lets
not go there again). That way they will only affect your application and the
default cfg file will also not get updated.
Rodney Wise provided OPAL code to do this a long long time ago now.