But as soon as I selected the target database, I got the same dialog telling me it could not upsize without setting the compatibility level. Interestingly though, when I clicked out of the dialog box, it moved on and let me run the wizard ran to completion. It appears the upsizing process worked fine - the SQL tables were created, and the data was transferred as specified.
Which is a good thing, because I don't think it's even been possible to set compatibility to level 6.5 in versions of SQL Server since 2005. So using the revised wizard appears to be a valid workaround, but it would be nice not to have to click past that dialog.
--stein
Comments: ** Comment from web user: Steingo **
We looked at this issue at the last MadFox user group meeting. The dialog is triggered whenever you run the wizard against newer versions of SQL Server since they no longer support older compatibility levels - so the attempt to set 6.5 compatibility will always fail. While it appears that basic table conversions work fine without resetting compatibility, it's possible that you could encounter issues if you are trying to preserve other database features like relationships, triggers, or validation rules.
So it may be appropriate to display the compatibility dialog but we think the wording should be changed. If the target is a newer version of SQL Server, it should inform the user that 6.5 compatibility is not supported, that there may be issues with certain features, but that they can proceed with basic conversion operations.