You will also likely encounter issues displaying the date fields because they are stored as datetime fields in SQL server. We use Visual Maxframe 2005. There are some helper datetime textbox objects that allow you to only display the date portion of the datetime field, will handle storing NULLS to the empty date fields, etc.

And when using Maxframe n-tier, there are also some hooks such as the business objects and data source saveaction() methods that give you a convenient place to replace all the empty dates with null right before sending the updates to SQL Server.



>I am converting a production VFP application (dbf's) to change to an MS SQL backend. The process of upsizing has it's issues, like dealing with empty date fields. All of the reading about this subject seems to be a one way street. That is, what you need to be doing to get upsized as a one-time- process. Some suggests that all empty date fields need to be converted to Nulls, others suggest that the ODBC driver will not allow nulls to be passed to MS SQL. So, now I have remote views talking to the MS SQL backend and any date field left empty, or changed to empty by the app, needs to have code attached checking for Nulls or 01/01/1900. Surely somebody has a solution for this "first day of upsizing" problem.
>
>Any suggestions would be helpful.
>
>Thanks
>
>Dallas