Re: "unique table" problem

It is OK to mix BetterADO with other ADO components. Every ADO dataset works
with own ADO recordset, unless you do not use something like:

DataSet2.Recordset := DataSet1.Recordset;

If you will want to replace all TADODataSet to TBetterADODataSet, use
GExperts (http://www.gexperts.org/).

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"Keith G Hicks" <krh@xxxxxxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:42c170b4$1@xxxxxxxxxxxxxxxxxxxxxxxxx
>2 other questions:
>
> 1. Last night I ended up setting the UniqueTable in the AfterScroll event
> of
> the TAdoDataset and it seems to work just fine. Does anyone see any
> problem
> with that?
>
> 2. Is it ok to mix BetterADO with just regular TAdoDataset in same forms
> and
> application? I don't need it everywhere and am not going to go changing
> it
> all through my current project. Just too much work.
>
> Thanks,
>
> Keith
>
> "Viatcheslav V. Vassiliev" <support@xxxxxxxxxxxxxxx> wrote in message
> news:42c1557a$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> Try BetterADODataSet (http://betterado.hit.bg/), it has property
> Unique_Table and will set it after activating dataset.
>
> //------------------------------------------
> Regards,
> Vassiliev V. V.
> http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
> ADO.Net
> http://www.oledbdirect.com - The fastest way to access MS SQL Server,
> MS Jet (Access) and Interbase (through OLEDB)
>
>
>
>


.

Relevant Pages