>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

I understand your frustration - as I've had to deal with the same issue before.
What I did to get around the problem (and I admit this is lame) - is changed all my .null. dates in my VFP tables to 01/01/1900...that will get you around the upsizing problem. (Phase I)
As far as your VFP application goes, (Phase II) - you'll have to come up with same way to deal with the issue. I've handled this a couple of different ways - it really depends on the nature of your app.