ADO doesn't do cached updates.
What about using a calculated field in the ADO Query for the check box
field.
Would that work?
> -----Original Message-----
> From: Tony Blomfield [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 10, 1999 2:47 PM
> To: Multiple recipients of list delphi
> Subject: [DUG]: ADO Query Question
>
> HI.
>
> Heres the problem.
>
> Imagine a query like this
>
> Select 'T', Description from Sometable
>
> The reason for the pseudo first column in this case is simply so we can
> set
> a checkbox in a DB grid. The user can walk up and down the grid checking
> or
> unchecking items, then when he clicks OK, processing takes place
> based on the check box value.
>
> With BDE this is easy, just turn Cached Updates on and never apply the
> updates, or use a ClientDataset.
>
> I am having trouble getting this to work with ADO (Obviously I dont
> understand ADO!) ADO is smart enough to recognise the first column as not
> really existing and complains bitterly.
>
> Basically I want the user to be able to play with any dataset with
> complete
> disregard for the underlying database object properties.
>
> Has anyone else confronted this issue? I could hook a Client Dataset up to
> the ADOQuery, but suspect that I might be mising something obvious and
> there
> is something I can do directly to ADO query to fully isolate it.
>
> My cursor is set to client side, and the Provider is SQLOLEDB.1
>
> Any ideas?
>
> Thanks,
>
> Tony.
>
>
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
