🚀 go-pugleaf

Hi Renato,
Please see my comments below.

"Renato Martins" <renato@griaule.com.br> wrote in message
news:3c435a77_2@dnews...
> Well, I've recently ran into lots of trouble with BDE. In particular, with
> some strange versions of Oracle client, among other things.

We also use Oracle.  BDE proved unreliable when, for example, a service app
that runs *forever* uses the BDE.  It loses memory and stops working.

>
> And, given the fact BDE will not have no more updates (only bug fixes),
I've
> decided to start using ADO.

I don't think they even do bug fixes any more.  They certainly couldn't help
me.

>
> Is it a hard migration? I basically use some TDatabase, TTable, TQuery,
and
> one TBatchMove. No data controls in my app (it�s sort of a service app).

We converted last year.  175 executables and over 350 forms.  Yes, it was a
bit painful.  Some things work a bit differently, some object methods are
different or not available.  We didn't use TBatchMove or TTable at all.
It's largely a function of how much code you have.

> Is there any site, paper or something which helps describing the migration
> path? I already use ADO, in ASP development. From what I saw of the
> components, it seems very similar...

I don't know of any.

>
> Will ADO connect easily with **any** database? Or are there some
> database-specific issues to be addressed?

Yes and no.  Not all DB vendors have an OLEDB provider available and some
that do are sadly lacking in functionality.  We use Oracle's OLEDB provider
(v8.1.7, didn't work well in 8.1.6) with reasonable success.  But IBM's DB2
OLEDB provider doesn't support BLOBs so we have to use the MS generic OLEDB
provider for ODBC, and IBM's ODBC driver for DB2.  Kind of goes down hill
from there.

Good luck!
- Arnie

>
> Any help would be greatly appreciated.
>
> Thanks,
> Renato
>
>