import

[Jeff Harrison]

--- Joe Chasan <joe at magnatechonline.com> wrote:

> On Tue, Jan 10, 2006 at 07:18:19AM -0800, Steven
> Waters wrote:
> > here is my code 
 
[snip]
  
> 
> with f=255 there is no imp(2) - you chose 255 as
> FIELD separator simply
> because it was unlikely to be used and you'd then
> have everything stuffed
> into field 1 - the idea that i think jeff was
> implying was that you'd then
> have to pick apart imp(1) via mid to put it into
> proper fields.
> 
> what i don't understand is that if you can get it
> into excel, why don't
> you just use the csv export from excel (see save-as
> dialog box)?
> 

Right.  Actually, I was more than implying, I stated
it outright earlier on.  You would need to parse out
imp(1) with this approach.  

There are potential problems with a CSV export from
excel.  If quotes appear in the data it could mess
things up I believe.  I would either stay with the
fixed length export or else use tab delimited or some
such.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.


		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com