>Terry,
>
>Would scenario would "require" INSERT INTO rather than APPEND BLANK?
INSERT INTO rather than APPEND BLANK would be required if an APPEND BLANK produces invalid data, for instance, a rule that forbids blank records, or an RI-rule.
The above, however, applies only if you don't use buffering. At least, I don't use field and record-validation rules, but with buffering, triggers are only evaluated when you TableUpdate().
>
>>This maybe one of those tables that requires an "INSERT INTO" because of a function ebeeded in the structure. Do a modi structure and check for a function call in the "default value"
>>HTH
>>>I have a program (PRG) that has a fatal exception error every time at the same exact point in the program, the APPEND BLANK command. This is an Accounts Payables Transaction Posting program.
>>>
>>>What did I do wrong? Any ideas on this one?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
