>I'm converting an application from using a VFP database to a SQL Server 2005 database. Is the upsizing wizard the recommended way of building the SQL Server data tables and transferring the data? Is there anything that it won't do for me? Apparently I will have to rewrite my triggers. Does the VFP referential integrity code transfer well, or should I redo that in SQL Server?

There are a number of gotchas with using the Upsizing Wizard. While it may make a good starting point for relatively simple VFP databases, you may encounter one or more of the following:

1) size issues: not only does VFP allow for tables wider than allowed in SQL, the upsizer limits the max width to about a quarter of what is legal in SQL.
2) You already know about the trigger issues, but be careful of indexes and SP's that use VFP-specific syntax
3) SQL reserved words used as table or field names will have an underline character added
4) Be careful of empty date values. These will be translated as "1/1/1900" in SQL. This may or may not be valid in your system.

RI code should transfer, with the caveat regarding VFP-specific functions.

Just some quick thoughts. I've used it, but nearly always construct either a VFP program or use DTS to transfer production data in the end.