I am using remote views and have not had a problem with this with VFP forms and controls. I am now using a commercial framework. I believe the root of the problem is in the framework.

I am tracing through code now to try to find the problem.

>Dan,
>
>>What is the proper syntax to specify an empty date value for a default value for SQL Server 7.0 datetime fields?
>
>SQL Server doesn't support an empty datetime in same sense that VFP does. If you set a SQL Server datetime datatype to "empty" you'll end up with a Jan 1, 1900 value. If it truly has to be unknown, you're best bet is to use NULLs.
>
>>Why can't I edit the values on my VFP forms if the SQL Server values are NULL? BTW, this problem occurs with ALL of my field types.
>
>That's a good question. Are you using remote views? Can you create a test using the VFP base form and edit the data?
>
>-Mike