When dealing with files of that size, I've always done just that. Split the file into reasonable chunks that I then process for whatever backend it is destined for.

Michael Oke, II

661-349-6221

Contents of this and all messages are intended for their designated recipient.

On Feb 21, 2012, at 8:37 PM, "MB Software Solutions, LLC"<mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:

> On 2/21/2012 8:07 PM, MB Software Solutions, LLC wrote:

>> What do you do when you have to import a text file that equates to a

>> cursor/table too big (beyond 2GB)? I'm using MySQL's import which is

>> fine for such huge beasts, but the import isn't liking some of the field

>> formats (related to my last post but not exactly that) and so I was

>> going to use VFP as the intermediary to massage/fix the data, then put

>> it into the MySQL table.

>>

>> Ideas? tia,

>> --Mike

>>

>> (VFP9SP2)

>>

>

>

>

> I know I could physically cut the file in half (or more pieces) and

> import that way then insert the parts to the final MySQL table, but I

> wondered if anyone had other ideas?

>

> tia,

> --Mike

>

> --

> Mike Babcock, MCP

> MB Software Solutions, LLC

> President, Chief Software Architect

> http://mbsoftwaresolutions.com

> http://fabmate.com

> http://twitter.com/mbabcock16

>

[excessive quoting removed by server]

_______________________________________________

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/BD5D4AC4-E55F-45E4-AA24-9886588AE485@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.