Thread View: comp.lang.pascal.delphi.misc
3 messages
3 total messages
Started by Marc Adams
Thu, 17 Sep 1998 00:00
Re: BDE Drivers
Author: Marc Adams
Date: Thu, 17 Sep 1998 00:00
Date: Thu, 17 Sep 1998 00:00
33 lines
1895 bytes
1895 bytes
Hello :( Unfortunately, I am having a problem installing the correct MS Access driver using Install Shield. PROBLEM: Even though the DAO 3.5 is installed on the target machine, when my application is installed with the BDE (using Install shield), MS ACCESS always selects the IDDAO32.DLL driver, in preference to IDDA3225.DLL. How can I change the Default driver?? SOLUTION: I can manually use the BDE administrator to change the MS ACCESS driver - and the application then works fine. Obviously this is not adequate for an installation. I am not sure where the problem is: 1) The DAO set-up ? But when selected the driver does work 2) The Install Shield installation ? 3) The registry or BDE config files ? I would be very grateful if anybody could shed light on this problem, maybe just point me in the right direction.. (To e-mail use remove *NOSPAM* from: M.Adams@sdxplc*NOSPAM*.com) Thanking-you Marc Adams
Re: BDE Drivers
Author: Bernd Maierhofer
Date: Thu, 17 Sep 1998 00:00
Date: Thu, 17 Sep 1998 00:00
24 lines
1723 bytes
1723 bytes
There has been a thread on this. Sefan from IS offered a solution with messing around with the SWDEPENDANT.INI of IS. Do a search at dejanews. HTH Bernd Marc Adams schrieb in Nachricht <3600B195.2518C92A@mcmail.com>... >Hello :( > >Unfortunately, I am having a problem installing the correct MS Access >driver using Install Shield. > >PROBLEM: >Even though the DAO 3.5 is installed on the target machine, when my >application is installed with the BDE (using Install shield), MS ACCESS >always selects the IDDAO32.DLL driver, in preference to IDDA3225.DLL. > >How can I change the Default driver?? > >SOLUTION: > >I can manually use the BDE administrator to change the MS ACCESS driver >- and the application then works fine. Obviously this is not adequate >for an installation.
Re: BDE Drivers
Author: Krzysztof Borys
Date: Fri, 18 Sep 1998 00:00
Date: Fri, 18 Sep 1998 00:00
56 lines
2625 bytes
2625 bytes
On Thu, 17 Sep 1998 07:52:05 +0100, Marc Adams <mia@mcmail.com> wrote:
>Hello :(
>
>Unfortunately, I am having a problem installing the correct MS Access
>driver using Install Shield.
>
>PROBLEM:
>Even though the DAO 3.5 is installed on the target machine, when my
>application is installed with the BDE (using Install shield), MS ACCESS
>always selects the IDDAO32.DLL driver, in preference to IDDA3225.DLL.
>
>How can I change the Default driver??
>
>SOLUTION:
>
>I can manually use the BDE administrator to change the MS ACCESS driver
>- and the application then works fine. Obviously this is not adequate
>for an installation.
>
>
>I am not sure where the problem is:
>1) The DAO set-up ? But when selected the driver does work
>2) The Install Shield installation ?
>3) The registry or BDE config files ?
Using DAO 3.0 is default configuration that BDE set at begin.
Try to use following code :
var
Cursor: HDBICur;
ConfigDesc: CFGDesc;
begin
Check(DbiOpenCfgInfoList(nil, dbiREADWRITE, cfgPERSISTENT,
PChar('\DRIVERS\MSACCESS\INIT'), Cursor));
try
while DbiGetNextRecord(Cursor, dbiNOLOCK, @ConfigDesc, nil) = 0 do
with ConfigDesc do
begin
OemToChar(szValue, szValue);
if (AnsiCompareText(szNodeName, 'DLL32') = 0) and
(AnsiCompareText(szValue, 'IDDAO32.DLL') = 0) then
begin
StrPCopy(szValue, 'IDDA3532.DLL');
CharToOem(szValue, szValue);
Check(DbiModifyRecord(Cursor, @ConfigDesc, true));
Break;
end;
end;
finally
DbiCloseCursor(Cursor);
end;
After this you must restart program.
UIN:3620584 Bask
mailto:bask@kis.p.lodz.pl
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads