This is an update to the Visual FoxPro 9.0 SP2 Upsizing Wizard. To launch the new wizard run the 'UpsizingWizard.app' from this location.

Review article on CODE Magazine: http://www.code-magazine.com/Article.aspx?quickid=0703052

This Sedna update release includes:

• Updated, cleaner look and feel
• Streamlined, simpler steps
• Support for bulk insert to improve performance.
• Allows you to specify the connection as a DBC, a DSN, one of the existing connections or a new connection string.
• Fields using names with reserved SQL keywords are now delimited.
• If lQuiet is set to true when calling the wizard, no UI is displayed. It uses RAISEEVENT() during the progress of the upsizing so the caller can show progress.
• Performance improvement when upsizing to Microsoft SQL Server 2005.
• Trims all Character fields being upsized to Varchar.
• BlankDateValue property available. It specifies that blank dates should be upsized as nulls. (Old behavior was to set them to 01/01/1900).
• Support for an extension object. This allows developers to hook into every step of the upsizing process and change the behavior. Another way is to subclass the engine.
• Support for table names with spaces.
• UpsizingWizard.APP can be started with default settings (via params) for source name and path, target db, and a Boolean indicating if the target database is to be created.

Visit project's home page...

2012.12.06 Release includes these updates:
This update has the following bug fixes:

• Handles converting Memo to Varchar(Max)
• You can now change the date used in SQL Server for empty VFP dates in one place: SQLSERVEREMPTYDATEY2K in AllDefs.H
• One of the export mechanisms ("JimExport") used null dates rather than the defined date for blank VFP date fields. This was fixed.
• The progress meter now correctly shows the progress of the sending data for each table.
• A bug that sometimes caused an error sending the last bit of data for a table to SQL Server was fixed.
• You no longer get a "string too long" error when using bulk insert with a record with more than 30 MB of data.
• You can now use field names up to 128 characters; the former limit was 30.