OK, now I understand what you are saying (it's monday, please be indulgent :)

So you do a INSERT INTO with blank values for all fields. What are the advantages of using INSERT INTO vs APPEND BLANK in that situation? Using INSERT INTO means that you have to include one value for each field of the table in the right order (if you are not specifying the field list). If you add a field, you will have to modify the code to match the new table structure while you will have nothing to modify with a APEND BLANK. So I'm curious to know what advantages INSERT INTO have to make this inconvenient a smaller one.

>I'm confused and AFVFP right now to not be able to test but I don't seem to recall a problem with INSERT INTO creating a blank view record. In fact, I never use APPEND BLANK anymore.