Re: SetConsoleCtrlHandler called when accessing ODBC/OLEDB datasource

> How about to switch to native OleDB provider for DBF file

No problem as long as it works.
It has to talk to dBase IV data _and_ index file (mdx).

> (I believe FoxPro have one)?
> Jet OleDB provider also could talk to DBF files.

As far as I know, Jet engine is only able to read simple DBF (no index)
file.
And foxpro has a different index type.

Note that I configurer the data source using Microsoft diver for dbf and
this driver use Borland code thru ODBCJT32.dll which is Microsoft driver.

--
francois.piette@xxxxxxxxxxx
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be

"Vitali Kalinin" <vitkalinin@xxxxxxxxx> a écrit dans le message de
news:42de0cdd@xxxxxxxxxxxxxxxxxxxxxxxxx
> "Francois Piette [ICS & Midware]" <francois.piette@xxxxxxxxxxx>
> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
> news:42de0484$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> > > I have a console mode application which behave badly when accessing a
> DBF
> > > file using a TAdoQuery. After hours of searching, I found that
TAdoQuery
> > > call SetConsoleCtrlHandler API function when accessing a DBF file for
> the
> > > first time. Of course this call override my own handler and therefore
> the
> > > application doesn't work as expected. This doesn't happend when
querying
> > an
> > > Oracle database.
> > >
> > > Any idea why SetConsoleCtrlHandler is called and how to avoid this ?
> >
> > I've discovered that BANTAM.DLL (Borland Local Engine) call
> > SetConsoleCtrlHandler to install his own handler, ignoring any handler
> > already installed. The Borland handler call ExitProcess directly. So my
> own
> > handler is not called, not any of the finalization section ! Very bad
> > behaviour.
> >
> > Any workaround available ?
> >
> > --
> > francois.piette@xxxxxxxxxxx
> > Author of ICS (Internet Component Suite, freeware)
> > Author of MidWare (Multi-tier framework, freeware)
> > http://www.overbyte.be
> >
> >
> How about to switch to native OleDB provider for DBF file (I believe
FoxPro
> have one)? Jet OleDB provider also could talk to DBF files.
>
>


.

Relevant Pages

  • Re: SetConsoleCtrlHandler called when accessing ODBC/OLEDB datasource
    ... >> How about to switch to native OleDB provider for DBF file ... As for dBase IV it should work as for _and_ index file I am not sure. ... >> Jet OleDB provider also could talk to DBF files. ... > this driver use Borland code thru ODBCJT32.dll which is Microsoft driver. ...
    (borland.public.delphi.database.ado)
  • Re: SetConsoleCtrlHandler called when accessing ODBC/OLEDB datasource
    ... > Also how about to load BANTAM.DLL explicitly, ... > before establishing yours handler to Console events? ... >>> How about to switch to native OleDB provider for DBF file ... before establishing yours handler to Console ...
    (borland.public.delphi.database.ado)