Export

[Richard Kreiss]

To all,

Although it is not supposed to happen, there appears to be a difference
between the export ascii and export word options.

In this case, size does make a difference.  

I have a file with over 107,000 records, 14 fields, which when completely
exported creates a file of just over 10 MB.

Apparently export word can't export this much data as it stops at 3MB of
data.  Using this function, I got just over 26,000 records and the last one
was only the first 3 fields.  The interesting part is the output continued
although the export file was not excepting any more data.  FilePro did not
indicate that there was/is a problem. 

This problem may relate back to the size a merge file can/could be.

Once I changed to export ascii, the complete file was exported.

Now a non-profile issue:

Imported the csv file into Access 2007, as my client is analyzing some data
using pivot tables.  In MS's inimitable way, it screwed up the import by
separating Jones Jr. (one field) in 2 columns. About 100 instances of this
type. This messed up the rest of the data for that record.

To eliminate the problem, I had to save the csv off as an excel worksheet
and then import that into Access 2007.  This worked.

The file created was just over 46MB.  When saved in Access 2003 format(mdb),
the file is 23MB.

This database started life as an Access database but was missing data for
them to do a proper analysis.  The missing data is in filePro so I imported
the data, updated it, then exported it for them to use.

This is a onetime thing otherwise fpodbc would work nicely for getting the
missing data into the file.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net