Board index » delphi » Disadvantages?: Delphi ADO and MS SQL Server 7.0/2000

Disadvantages?: Delphi ADO and MS SQL Server 7.0/2000

   Are there any major problems with using Delphi's ADO objects
and MS SQL Server 7.0 or 2000?  So far, I haven't seen any.
I was even able to update a multi-database table join through a
data bound control without using cached updates or a client dataset.
Anybody notice any problems with this configuration?

Thanks,
Chad Noles

 

Re:Disadvantages?: Delphi ADO and MS SQL Server 7.0/2000


it screams for me, both with remote client type apps and local, batch style
server apps.

Re:Disadvantages?: Delphi ADO and MS SQL Server 7.0/2000


Works great for me.

--
Michael Rodriguez
Compeat Restaurant Accounting Systems
http://www.compeat.com
m...@compeat.com

Quote
"Chad Noles" <cno...@btg.com> wrote in message news:3aeed068_2@dnews...
>    Are there any major problems with using Delphi's ADO objects
> and MS SQL Server 7.0 or 2000?  So far, I haven't seen any.
> I was even able to update a multi-database table join through a
> data bound control without using cached updates or a client dataset.
> Anybody notice any problems with this configuration?

> Thanks,
> Chad Noles

Re:Disadvantages?: Delphi ADO and MS SQL Server 7.0/2000


    If I remember correctly, Borland ADOExpress and BatchUpdates in a M/D
relationships has some bugs. I myself use ClientDatasets for my M/D's. Other
than that ADO does work pretty well against MS Databases.
--
Sunil Furtado
New Mangalore Port Trust
Quote
Chad Noles <cno...@btg.com> wrote in message news:3aeed068_2@dnews...
>    Are there any major problems with using Delphi's ADO objects
> and MS SQL Server 7.0 or 2000?  So far, I haven't seen any.
> I was even able to update a multi-database table join through a
> data bound control without using cached updates or a client dataset.
> Anybody notice any problems with this configuration?

> Thanks,
> Chad Noles

Other Threads