Jon,

SQL Server considers empty date and string fields as NULL not empty(). Therefore if any of those fields contains empty rows the wizard will make the field except NULL values. There are many of these stituations that must be resolved when upsizing. If you plan on going to Oracle start converting all your logical fields to integers. Logical data type fields to not exist in Oracle.

First thing to do is change all datetime fields in VFP to allow nulls. Working with VFP, SQL Server and Oracle data sources for the past four years I find it much easier to keep the data sources as alike as possible. If you have a large number of tables in the database it is easier to write a program to do the conversion. I've got the code somewhere if you want an example.

>I went through a test run on upsizing our database (VFP7 to SQL2K) and am now starting to go through the error report to check things out.
>
>One thing I noticed a few times is that there was a problem trying to create a primary key constraint on a nullable column in a table. When I look at the structure in VFP, the column in question is not checked off as allowing null values. Yet, when I look at the table design in SQL the column is marked as allowing nulls. With one table it's a character field and in another it's a date field.
>
>What would trigger the upsize wizard to make the column nullable in SQL? Should I be checking somewhere in the RI for this?
>
>Any info would be greatly appreciated.
>
>Laterness,
>Jon