Hiya Sylvain

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

Yeah...I know...Monday....bleeeah :-)

>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?

No I don't. But I do insert with fields that require a value as defined in my database constraints.

>Using INSERT INTO means that you have to include one value for each field of the table in the right order

No, no. You can use INSERT INTO with whatever fields you want in whatever order. For example, if I have defined a rule for a field in the DBC() such as !EMPTY(field) then I *have* to use INSERT INTO (field) VALUES (value) because APPEND BLANK will generate an error.