Thanks for your reply, John. But (you knew that was coming!) I don't think VFoxpro should CARE what the remote database engine thinks. At least as far as its own stability. Maybe you missed it, but VFP doesn't produce just an error message, it shuts itself down. Completely. Its gone. And probably not very cleanly.

I will gladly program around the limitations of the remote data engine(sybase SQL anywhere), but would think that VFP should be stable enough to just return an error if I try to insert a null value by mistake.

(Egads! I think I may be whining. I hate that. Its been a long week of long days. I think I'll go home now :-)

>Could be the "Allow NULL" settings on your server database. Some databases don't like numeric or date blanks AT ALL.
>
>
>>If I SCATTER memo memvar and then insert into (remoteviewtable) from memvar and I have null or empty fields in the orginal table, VFP crashes. This is quite a pain, since I can't scatter to an array.
>>
>>If I release the memo variables that are null or empty, then the insert from memvar works. Anyone got any insight on what causes this? I'll accept it as standard behavior, but I want to know why it happens. Why don't I get an error message? Why does VFP die?