Well the fields vary. But what I actually did is include all the fields of the free table in the SQLExec statement and then have a gridview that shows only the ones they may add/edit. That solved the problem. It was a little bit of extra coding but its become even more flexible.

Costas

>>Hi everyone,
>>
>>I have a not so strange situation where I create a cursor using SQLEXEC() from a FREE DBF table. Only a few of the fields are used in the SQL statement. I then add records to the cursor using APPEND BLANK and execute TABLEUPDATE().
>>
>>However the rest of the fields which were not part of the cursor are set to .NULL. in the free DBF table. This cause problems with apps that don't expect the NULL values.
>>
>>Is there some property where I can set to force all the fields to be initialized to the blank values?
>>
>>Thanks for your help.
>>
>
>Costas,
>How many extra fields are we talking about? Can you include them in the SQLExec statement and use the NVL() function to make them ''?