Re: COMMIT recors instead of a complete form

I believe that this could be solved with a call to the POST-procedure. It POSTs changes to the database, but do not perform a COMMIT. But that might not help, when I think about it more in detail...

Lars

Arie Mars skrev i meddelandet <835rq4$bpkd$1_at_reader1.wxs.nl>...
>Hello,
>
>Some questions about COMMIT
>
>1. Why is the message 'No changes to save' a popup-message sometimes,
>instead of a status-line message?
>
>2. I use a timer-trigger in my FORM to start an import procedure, running
in
>the background.
> In this procedure I use some SQL code to INSERT the imported values
INTO
>the database.
> After that I use a COMMIT. This will not only commit the new values,
but
>it tries to COMMIT
> all datablocks (in fact the whole form). So when the user is modifying
>data on some
> datablock/canvas at the same time, his/her changes will be committed too
>at that moment.
> I don't want this. My procedure must commit its own records only.
>
>
>Thanks in advance
>
>Arie Mars
>arie_at_pca-online.nl
>
>
>
Received on Tue Dec 14 1999 - 23:46:18 CET