Thanks Sergey,

This is definatelty a problem with the Sybase Patch. I did some checking with an older version and found different results.

* new version of ASA. 
?SQLEXEC(con,"select NULLIF(f1,NULL),f2 from #test","res") && this works
?SQLEXEC(con,"select NULLIF(f1,NULL)as f1,f2 from #test","res") && this does not work.
* old version of ASA. 
?SQLEXEC(con,"select NULLIF(f1,NULL),f2 from #test","res") && this works
?SQLEXEC(con,"select NULLIF(f1,NULL)as f1,f2 from #test","res") && this works.

>Hi James,
>
>A column in a cursor is marked as nullable if when it comes as nullable from a backend. See Re: Remote view redefine field to support NULL Thread #789213 for the relevant discussion.
>
>
>>Hi All
>>
>>VFP8.0.
>>
>>I have just hit one that I can’t figure out and I don’t think it is a VFP problem but I need so help with how VFP works so I can get this working again. I am using Sybase Adaptive Sever Anywhere for my database. I have been using this database for years without problems. I use SQL pass through for all my data access. I change buffering to 5 on all my cursors that I wan to update to track what rows have been changed.
>>
>> Friday, I upgraded to a new version (a patch or bug fix) and started getting an error doing a replace that said a column cannot be null when the database says it can be. It seems that using a multi-table join for a query causes the problem. If I just use a select * from table I don’t see this problem. My question is how does VFP decide if a column in a cursor should be nullable or not and if there is a way to override this behavior.
>>
>>Thanks.