|Subject||Re: [IBO] Simple Question about delete clause|
If you use this approach from Helen, your grid will not be 'advised' from the changes, so as all others TDataSet components. I spend hours looking why one day...
----- Original Message -----
From: Helen Borrie
Sent: Wednesday, September 05, 2001 4:38 PM
Subject: RE: [IBO] Simple Question about delete clause
At 05:05 PM 05-09-01 +0200, you wrote:
>Its not my day to day unfortunately I am not using ib_dataset but ibodataset
>because I am tied to a specific grid(devexpress) so all of these nice
>and stuph is not available to me. I looked or tried at the tdatasets refresh
>procedure and it does not look like it has something similar to
>raInvalidateCursor I also tried the InvalidateBookMark but to no avail it
>gives me the same error.
>Any other ideas.
>Thanks for the help so far.
> > Uh-huh, OK. :-) Call InvalidateBookMark on the dataset when you
> > call the delete procedure; or change the dataset's RefreshAction
> > to raInvalidateCursor . This tells IBO that it will have to
> > check for that row's existence if it gets referred to again.
> > Closing and opening the dataset is an EXTREEEEEEEME way to kill a
> > cat. You are possibly getting this particular reaction from
> > having something like CommitAction as caRefresh and RefreshAction
> > as caKeepDataPos (can't say exactly except "I have been there". :-))
> > hth
> > Helen
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
Yahoo! Groups Sponsor
You can, too! Start here...
345678 ft 01234567891011in
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]