[turba] RE: Import Turba Contacts

[Ryan Burton]

Thanks for the help and the replies.  I started filtering through my csv
file and trimming it down to try and find where it was messing up.  When
I export the file, it has 92 fields.  When I attempt to import that into
turba, it counts 86 fields, and the first couple of rows that are
displayed show double quotes around the each field, separated by commas.
Then if I clicked next, I get the error I described originally, and if I
change it to 92 fields, I also get the same original errors.

So, if I go into the csv file and delete the last column, which is 'web
page', then try to import it, there are now no quotes around the fields,
but I still get the same errors.  Then I started to delete one column at
a time starting at the end, so I went through 'User 4', 'User 3', 'User
2', 'User 1', 'Spouse', all of which were empty, until I reached the
last column that had data in it.  When I went to import it then,
everything worked fine, and I received none of my original errors.  So I
went back to the original csv file and added data in the last columns,
thinking there might be an issue with that, but I got the same errors.  

My conclusion:  horde (or File_CVS), doesn't import well with more than
86 fields.

Also, when it finally did import, the first 14 contacts were duplicated.
So maybe it's an issue with my csv file, and/or File_CVS.  At any rate,
it wasn't easy to get working.  Thanks for all the help though.  Ciao.

Ryan.

-----Original Message-----
From: turba-bounces at lists.horde.org
[mailto:turba-bounces at lists.horde.org] On Behalf Of Jan Schneider
Sent: Friday, November 28, 2003 3:27 PM
To: turba at lists.horde.org
Subject: Re: [turba] RE: Import Turba Contacts

Zitat von Mike Bydalek <mbydalek at zivix.com>:

> > Can anyone help me solve this problem??
> After taking just over 1000 contacts and importing them into Turba, I
> found out
> some interesting things that I still have to go over and figure out
> "why?" they
> were happening.
>
> For one, Turba is REALLY picky about the formatting of each field.
For
> example,
> using CSV, if there was an entry for "Address" without a comma, it
> wouldn't
> like it.  If there was a phone number with improper formatting, Turba
> would
> kick back errors.
>
> All I can really say is to try and comb through your data as best as
you
> can
> (with 1000 it took me forever) and make sure that each field is
properly
> formatted.  I broke up my data into 50-100 blocks and went from there.
>
> One thing that I think would help would be for Turba to say something
> along the
> lines "The field <whatever> is invalid on line <whatever>" or at least
> "There
> is an error in Record <whatever>" to help steer towards a problem.

The problem is that most of this is done by the File_CSV package or the
fgetcsv function. We have no influence on their behaviour.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft

-- 
Turba mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe at lists.horde.org