Hi Sylvain --

Yes, and also move from APPEND BLANK to INSERT INTO (fields) with whatever keys generated at the UI level placed into the new record.

A definitive solution though begs the question, where are primary keys generated? By Oracle Sequences or by the UI (VFP)?


>Try turning on table/record buffering. That way, the record won't be added until you issue a TableUpdate().
>
>HTH
>
>>I have a form that is all remote views on an Oracle database. To reduce network traffic, much of the buisiness processing is in the Oracle database. ( Oracle could use lessons in interface builder design from FoxPro!!)
>>My problem comes when I try to add a record. The default(wizard) behavior is to APPEND BLANK, which fails several integraty constraints and invalidates an after insert trigger.
>>My question is: is there an easy way to defer the insert until the data has been entered, or do I really have to go back to the old FP2.6 SCATTER/ GATHER syntax and m.field_name controls and full rewrite of the nav button behavior?
>>Any suggestions will be appreciated.