A couple of tips I remember from when I did this:

use a cursor / temp table at the fox end, which gives you the option to

do some pre-cleanup (e.g. truncate memo fields - I agree with the

suggestion to use Varchar instead of Text; maybe change date formats;

check pk's - you can import them if you set auto off at the SQL end then

set the start value when you set it on again; maybe re-normalise some

tables you had left un-normalised in VFP)

also use an intermediate work table at the SQL end for post-cleanup

(e.g. trim Char fields that are now Varchar) .... then wait for null

values to bite you in the ass!

If you are importing into an existing database turn off integrity

checks, triggers, SP's etc. wherever possible.

cheers

AndyD 8-)₹

On 15/05/2012 18:49, Kurt Wendt wrote:

> Although, in the end - I still had the warnings about the

> DefaultCodePage stuff - I finally reached success! The data was finally

> converted. Now I just need to see how the data looks in SQL - and if

> anything looks fine - hopefully just have to tweak and re-convert a

> couple tables instead of all of them.

>

> Thank you ALL - as this ProFox list Rocks as usual!

>

> -K-

>

> <snip>

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4FB2D0EA.1000307@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.