Re: About deleting.
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 03/26/05
- Previous message: Del M: "Re: How to add results to ADOQuery and DBGrid for browsing"
- In reply to: kolja2003: "Re: About deleting."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Mar 2005 22:01:31 -0600
>Those fields are from table Stock which I want to keep intact.
>I put in force your advice: ADOQuery.Properties['Unique
>Table'].Value:='Items'; meaning that update, insert, delete will enforce
>only on table Items and leave table Stock intact.
That is not correct. Although there are some references that say this Unique
Table property only affects Deleting records
>Then I execute: ADOQuery.Append and I get appended row in table Item and
>again in table Stock too! Just what I wanted to prevent by any means!
>After debugging I found that it happens because I have SORT in force.
>Since SORT includes the fields from table Stock despite I put "Unique Table"
>on another table, it still create index for appended row to table Items by
>default (I think) it invokes append to table Stock too as I has to use its
>datfield values for compose index.
>When I put "SORT:= '' " side effect disappears.
>May be it is bug?
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Previous message: Del M: "Re: How to add results to ADOQuery and DBGrid for browsing"
- In reply to: kolja2003: "Re: About deleting."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]