>If I'm not mistaken you could run into snag during the upsizing if any records in the original DBFs contain values that aren't strictly OK (e.g. invalid dates). Additionally blank values could might not transfer if the SQL dataabase specifies NOT NULL for osme of fieldes in the table.

Additionally, any *******.** is not a number in SQL-speak, it will also break the conversion. It also includes the cases where fox will stuff 3456.7 into a n(6,4) field - SQL doesn't use that trick, and if you have such numbers you must make the target column n(9,4) at least. The upsizing wizard usually adds 2 to the number of places, which helps but not always.