>>Hi Brenda,
>
>>to be comliant with ANSI SQL, you now must either list ALL the fields in >the insert statement, or make all the fields which you do not include, >nullable.
>
>Trying to understand the difference between the way it use to work and the way it works now. How does it affect my data. What was inserted before - NULL values? If not, how will NULL values possibly affect my code that accesses the table?
>
>Brenda

As I wrote in my last message, VFP9 is now even closer to ANSI SQL than before. You can fix this 'brutally' by either SET ANSI OFF or SET ENGINEBAVIOR 80, but I don't recommend that solution as anything but band aid. In the long run you should change your INSERTs. The thing is that for an INSERT where a field is not listed, the value is unknown. Unknown used to mean "blank", now unknown is .NULL.! I hope you understand the difference.