Export

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com
>
[mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com]
On
> Behalf Of Mike Schwartz
> Sent: Tuesday, July 01, 2008 10:19 PM
> To: 'filePro'
> Subject: RE: Export
> 
> > 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.
> >
> > Richard Kreiss
> > GCC Consulting
> > rkreiss at gccconsulting.net
> 
>     What are you using for the delimiter between fields?  Generally I use
> the pipe "|" sign, but sometimes the tilde "~".  If you use an "odd"
> character like that, you should be able to import the files into Excel or
> most other databases without ever seeing a "Jones Jr." error.
> 
> Mike Schwartz

The output was  a comma delimited file with quotes.  Standard Windows csv
output.

As I said, when saves as an Excel worksheet and imported into Access,
everything came in correctly.  Apparently, Access it too smart for itself in
assuming that Jr. or similar should be separated.  By the way, the import
left Jones III alone. The odd thing was it left the quotes opening in one
column and closing in the next.  One could probable write a script to
correct this anomaly but it was faster to use the solution I came up with.

Richard Kreiss