I read into a query some record and then I can edit them in that query.
After, I update table. I am wondering, if I delete a record in that query...
how can I "update" that record in table, since it has been deleted? Is this
aproach ok or am I missing somethig?
I use desktop 4.25 (not a C/S) and D6.

Andrej Bivic

"Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
news:4350A214-852F-425A-97E6-FB290D54E98F@news.elevatesoft.com...
>I read into a query some record and then I can edit them in that query.
>After, I update table. I am wondering, if I delete a record in that
>query... how can I "update" that record in table, since it has been
>deleted? Is this aproach ok or am I missing somethig?
> I use desktop 4.25 (not a C/S) and D6.
>

For deletes, you have to use the before delete. You are correct, after
delete it is too late.

Robert

> Andrej Bivic
>

Andrej,

> I read into a query some record and then I can edit them in that query.

I'm not sure if you mean this as a question or a statement. In case it
is a question ...yes you can edit the records in the query but the exact
effect of doing so will depend on whether RequestLive (and ResultIsLive)
is true and whether CachedUpdates are active.

> After, I update table.

How? Via the query or via some other mechanism (or user)?

 I am wondering, if I delete a record in that query...
> how can I "update" that record in table, since it has been deleted?

You can't update a non-existent record - you would have to re-insert it.

> Is this
> aproach ok or am I missing somethig?


I can't really tell exactly what you are trying to ask.

Eryk

I am aware of this. But, I would like to "have" a "Cancel" option, so user
can change his mind befor actually "posts" his changes, and that includes
deleteing. So, If you can suggest an aproach for inserting, editing and
deleting data in a query and, on a demand, posting everything into a table
or simply canceling everything.
A

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:F9509E4A-176D-426D-974B-9687BFE5A955@news.elevatesoft.com...
>
> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
> news:4350A214-852F-425A-97E6-FB290D54E98F@news.elevatesoft.com...
>>I read into a query some record and then I can edit them in that query.
>>After, I update table. I am wondering, if I delete a record in that
>>query... how can I "update" that record in table, since it has been
>>deleted? Is this aproach ok or am I missing somethig?
>> I use desktop 4.25 (not a C/S) and D6.
>>
>
> For deletes, you have to use the before delete. You are correct, after
> delete it is too late.
>
> Robert
>
>> Andrej Bivic
>>
>
>

"Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
news:2A23F037-8484-4A9C-A778-1D9A25EA45AA@news.elevatesoft.com...
>I am aware of this. But, I would like to "have" a "Cancel" option, so user
>can change his mind befor actually "posts" his changes, and that includes
>deleteing. So, If you can suggest an aproach for inserting, editing and
>deleting data in a query and, on a demand, posting everything into a table
>or simply canceling everything.

Add a "state" field to the query, 0 = not touched 1 = changed, 2 = deleted,
filter out the 2s so that they don't show on the grid but are still there in
the query, and when you are ready to post, remove the filter and go thru the
query, updating the state 1s and deleting the state 2s.

Robert

Yessss! This is what I was looking for. Just one thing more... how do I
filter a query in a way you've described?
Andrej

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:AB2886F4-0E87-42A6-8C8E-A3CB3F46DBBB@news.elevatesoft.com...
>
> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
> news:2A23F037-8484-4A9C-A778-1D9A25EA45AA@news.elevatesoft.com...
>>I am aware of this. But, I would like to "have" a "Cancel" option, so user
>>can change his mind befor actually "posts" his changes, and that includes
>>deleteing. So, If you can suggest an aproach for inserting, editing and
>>deleting data in a query and, on a demand, posting everything into a table
>>or simply canceling everything.
>
> Add a "state" field to the query, 0 = not touched 1 = changed, 2 =
> deleted, filter out the 2s so that they don't show on the grid but are
> still there in the query, and when you are ready to post, remove the
> filter and go thru the query, updating the state 1s and deleting the state
> 2s.
>
> Robert
>

Andrej,

> deleteing. So, If you can suggest an aproach for inserting, editing and
> deleting data in a query and, on a demand, posting everything into a table
> or simply canceling everything.

Query.BeginCachedUpdates
Query.ApplyCachedUpdates
Query.CancelCachedUpdates


Eryk

"Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
news:BFAA5461-1E99-44A4-BC11-F4896245A56E@news.elevatesoft.com...
> Yessss! This is what I was looking for. Just one thing more... how do I
> filter a query in a way you've described?

Query.Filter := 'State = 2';
Query.Filteres := true;

Update the state field on before post and before delete. On the delete,
you'll have to first abort the delete.

Robert

> Andrej
>
> "Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
> news:AB2886F4-0E87-42A6-8C8E-A3CB3F46DBBB@news.elevatesoft.com...
>>
>> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
>> news:2A23F037-8484-4A9C-A778-1D9A25EA45AA@news.elevatesoft.com...
>>>I am aware of this. But, I would like to "have" a "Cancel" option, so
>>>user can change his mind befor actually "posts" his changes, and that
>>>includes deleteing. So, If you can suggest an aproach for inserting,
>>>editing and deleting data in a query and, on a demand, posting everything
>>>into a table or simply canceling everything.
>>
>> Add a "state" field to the query, 0 = not touched 1 = changed, 2 =
>> deleted, filter out the 2s so that they don't show on the grid but are
>> still there in the query, and when you are ready to post, remove the
>> filter and go thru the query, updating the state 1s and deleting the
>> state 2s.
>>
>> Robert
>>
>
>

All that works fine!
Here is another question.... when I delete a record and filter it out, the
grid seems not to update the number of record, while it shows as many record
as there was befor deleting, although cursor can not be moved to the
"deleted" rows.
Please, advise.
Andrej


"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:89593EDD-F57B-4555-9C5B-2430F0ED8799@news.elevatesoft.com...
>
> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
> news:BFAA5461-1E99-44A4-BC11-F4896245A56E@news.elevatesoft.com...
>> Yessss! This is what I was looking for. Just one thing more... how do I
>> filter a query in a way you've described?
>
> Query.Filter := 'State = 2';
> Query.Filteres := true;
>
> Update the state field on before post and before delete. On the delete,
> you'll have to first abort the delete.
>
> Robert
>
>> Andrej
>>
>> "Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
>> news:AB2886F4-0E87-42A6-8C8E-A3CB3F46DBBB@news.elevatesoft.com...
>>>
>>> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
>>> news:2A23F037-8484-4A9C-A778-1D9A25EA45AA@news.elevatesoft.com...
>>>>I am aware of this. But, I would like to "have" a "Cancel" option, so
>>>>user can change his mind befor actually "posts" his changes, and that
>>>>includes deleteing. So, If you can suggest an aproach for inserting,
>>>>editing and deleting data in a query and, on a demand, posting
>>>>everything into a table or simply canceling everything.
>>>
>>> Add a "state" field to the query, 0 = not touched 1 = changed, 2 =
>>> deleted, filter out the 2s so that they don't show on the grid but are
>>> still there in the query, and when you are ready to post, remove the
>>> filter and go thru the query, updating the state 1s and deleting the
>>> state 2s.
>>>
>>> Robert
>>>
>>
>>
>
>

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?
Andrej

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:AB2886F4-0E87-42A6-8C8E-A3CB3F46DBBB@news.elevatesoft.com...
>
> "Andrej Bivic" <andrej.bivic@abitrade.si> wrote in message
> news:2A23F037-8484-4A9C-A778-1D9A25EA45AA@news.elevatesoft.com...
>>I am aware of this. But, I would like to "have" a "Cancel" option, so user
>>can change his mind befor actually "posts" his changes, and that includes
>>deleteing. So, If you can suggest an aproach for inserting, editing and
>>deleting data in a query and, on a demand, posting everything into a table
>>or simply canceling everything.
>
> Add a "state" field to the query, 0 = not touched 1 = changed, 2 =
> deleted, filter out the 2s so that they don't show on the grid but are
> still there in the query, and when you are ready to post, remove the
> filter and go thru the query, updating the state 1s and deleting the state
> 2s.
>
> Robert
>