Using dbCopy instead of Import for speadsheets.

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Scott Walker
> Sent: Monday, March 11, 2013 2:19 PM
> To: 'filePro Mailing List'
> Subject: RE: Using dbCopy instead of Import for speadsheets.
> 
> I will look at openoffice...it's got to be more sane than Excel.
> 
> Regards,
> 
> Scott
> 
> > -----Original Message-----
> > From: filepro-list-
> > bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
> > [mailto:filepro-list-
> > bounces+scottwalker=ramsystemscorp.com at lists.celestial.com] On Behalf
> > bounces+Of
> > Kenneth Brody
> > Sent: Monday, March 11, 2013 2:01 PM
> > To: Bob Simcoe
> > Cc: 'FilePro Mailing List'
> > Subject: Re: Using dbCopy instead of Import for speadsheets.
> >
> > On 3/11/2013 1:48 PM, Bob Simcoe wrote:
> > > Until recently, whenever I needed to import from an Excel
> > > spreadsheet ( every month, 7,000+ lines, 10 fields, , and " ), it was
very
> simple.
> > > Save the spreadsheet as a dbaseIV file and use fp's dbCopy. Then fix
> > > things up in Define Files and Screens. The reason I said  "until
> > > recently", was that new versions of Excel do not offer saving as a
> > dbase.
> >
> > OpenOffice.org can still read and write .dbf (as well as Excel) files,
> > should the need arise.
> >
> > On the other hand, doesn't Excel have the option to write
> > tab-delimited text files?  (Use "f=\t" in filePro.)

Under most circumstances OpenOffice is fine.  However, recently I ran into a
problem where open office failed.  I had to import a csv file of just over
144,000 rows.  Excel 2012 can handle that but no OpenOffice.


Richard Kreiss
GCC Consulting

Office: 410-653-2813