"Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
news:99163B99-614F-4634-ACC0-18388A93BAC8@news.elevatesoft.com...
>I am wondering... do I need fiur states?
> One for new records which are about to be inserted,
> another one for "old" records, which are about to be updated,
> another one for "old" records, which are about to be deleted
> and another one for "old" records, which are untouched.
>
> Am I right?

You are right.

Robert

Am wondering... let say, am I editing existing record in a query and after
that, want to update the record. What if that record has been deleted by
another user? What is the best approach?

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:45E9CEBD-31F4-4B50-8F46-F6BD486E0B55@news.elevatesoft.com...
>
> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
> news:99163B99-614F-4634-ACC0-18388A93BAC8@news.elevatesoft.com...
>>I am wondering... do I need fiur states?
>> One for new records which are about to be inserted,
>> another one for "old" records, which are about to be updated,
>> another one for "old" records, which are about to be deleted
>> and another one for "old" records, which are untouched.
>>
>> Am I right?
>
> You are right.
>
> Robert
>
>

Andrej,

<< Am wondering... let say, am I editing existing record in a query and
after that, want to update the record. What if that record has been deleted
by another user? What is the best approach? >>

Welcome to the wonderful world of change detection and resolution.

The way that we handle it with DBISAM is to simply issue an error and abort
the update.

--
Tim Young
Elevate Software
www.elevatesoft.com