COMMIT recors instead of a complete form

Some questions about COMMIT

[Quoted]
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. [Quoted] [Quoted] In this procedure I use some SQL code to INSERT the imported values INTO the database. [Quoted] [Quoted] After that I use a COMMIT. This will not only commit the new values, but [Quoted] it tries to COMMIT [Quoted] 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. [Quoted] 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 - 17:35:09 CET