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