Export

[Richard Kreiss]

From: Richard Hane [mailto:yoresoft at sbcglobal.net] 
Sent: Wednesday, July 02, 2008 9:10 AM
To: Kenneth Brody; rkreiss at gccconsulting.net
Cc: 'filePro Mailing List'
Subject: Re:Export

 



Kenneth Brody <kenbrody at bestweb.net> wrote: 

Quoting Richard Kreiss (Tue, 1 Jul 2008 11:17:25 -0400):

> I have a filepro file with 107,450 records, with 14 fields, that 
> needs to be exported to a csv file.
>
> When export word is run, is stops writing records after about 
> 28,600. The last record written has only the first 3 fields written.

What is the exact size of the resulting export file? Does your system
have some sort of file size limit that's being hit?

> Is there a limit to how many records can be exported?

No.

> Is there an export environmental variable that can be set.

No.

Ken, Rich

 

Sorry I got in to this thread so late but...

 

I must disagree with Ken (kind of).  A month ago when we moved to the new
version and a new server we discovered a similar situation.  It may not be a
filepro problem but import processes (from Excel to filePro) that have
worked here for years stopped working after the upgrade.

 

Funny thing is if you reduce the number of lines in the Excel worksheet to
around 30,000 they work great. 

 

fpTech asked me to send in the files but I didn't (my bad) it's just been
crazy around here with our plant move.

 

Rick Hane

DeLuxe Stitcher Company Inc

www.deluxestitcher.com

 

Rick,

 

 

Windows server 2003, Workstation running Win XP Pro with service pak 2.
Filepro 5.6 ODBC.

 

I was able, without trouble to import the csv file with just about 107,450
lines(records).  I created my filepro file and then imported the data.

 

This went smoothly.

 

Now one thing I would like with FPSQL is an option to output a CSV file from
a query.  This would make exporting to a csv file almost painless.
Especially in this case where I needed all of the records.

 

Since both Access and Excel 2007 can import xml, the new, yet unreleased
filepro xml program, would have worked here quite well. 

 

Richard 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20080702/ca541bd0/attachment.html