On 8/8/06, Iames Pizzoli <[EMAIL PROTECTED]> wrote:
> As far as LOAD DATA INFILE, more details from you would be
> useful before making a comment. LOAD DATA INFILE is good for
> one-time straight imports. But if you have to do validity
> checking, convert data, etc, you're probably better off with
> a routine. LOAD DATA INFILE isn't very intelligent. :)

        I'm using it and I find it useful. It's not a big problem for me
spend some time to do things manually, because it's basically a one-time
job.

What I have done in the past was to write a Fox program to open a
table, generate a CREATE TABLE command and scan through the table
generating INSERT INTO commands.  All this was saved into 1 big text
files and executed on the SQL server.  This way you can 'fix' the data
as needed.  For example, my dataset originated from DOS days and there
were a few invalid dates in there.  Also I did things like change
dates (and strings?) to NULL where they were empty.

--
Paul


_______________________________________________
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
** 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