Andy, 

Its kinda funny that - even though I already mentioned several times in this 
thread and the original thread that I was using the Import/Export Wizard to 
convert the data from VFP to SQL - I still keep getting people responding with 
advice on how to do the conversion via programming.

So - in case you missed that part - I actually used the SQL Server Import and 
Export Wizard to convert the data. Also, as my last post mentioned - I already 
was able to successfully convert the data - so the process in general is a 
non-issue.

I am, however, now in the process of looking at the data from both sides - just 
to see how well the conversion went - and then possibly making additional 
changes (like to the mapping of fields & structures) - and possibly run the 
conversion again.

However - I will add - that people keep mentioning this PK thingy - although I 
have no clue actually what it is...

-K-

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of AndyD
Sent: Tuesday, May 15, 2012 5:56 PM

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-
_______________________________________________
Post Messages to: [email protected]
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/289ea162f5642645b5cf64d624c66a140e260...@us-ny-mail-002.waitex.net
** 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.

Reply via email to