Re: TADOStoredProc
- From: Brian Bushay TeamB <BBushay@xxxxxxxxx>
- Date: Wed, 10 Oct 2007 20:30:47 -0500
Hi,
I'm not sure what you mean by "do not match up well"? We have a large client
suite that excusively uses TADOQuery and TADOStoredProc components for
database access. We don't appear to have any problems with the components
and they are easy-to-use.
For instance. TAdoQuery sets the SQL using a Tstringlist while TadoDataset uses
a Widestring;
While both can set the SQL in the underlying ADO dataset there is a performance
penalty if you set it one line at a time like AdoQuery.sql.Add('this line');
leads you to do
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- Follow-Ups:
- Re: TADOStoredProc
- From: Paul Scott
- Re: TADOStoredProc
- From: Dmitry Arefiev [da-soft.com]
- Re: TADOStoredProc
- References:
- TADOStoredProc
- From: Alan T
- Re: TADOStoredProc
- From: Brian Bushay TeamB
- Re: TADOStoredProc
- From: Niklas Larsson
- Re: TADOStoredProc
- From: Brian Bushay TeamB
- Re: TADOStoredProc
- From: Nigel Jones
- TADOStoredProc
- Prev by Date: Re: TADOStoredProc
- Next by Date: Re: TADOStoredProc
- Previous by thread: Re: TADOStoredProc
- Next by thread: Re: TADOStoredProc
- Index(es):
Relevant Pages
|