[turba] Turba RC1 issue

[Kent Martin]

It is probably a bit late to be bringing this up, but, the following is 
an excerpt  from an email I just
sent to the imp list.

Finally, an issue with turba import, so I will post the following over 
there as well.

When importing CSV, turba decides what fields are available by looking 
at the first
record.  I believe a rethink on this is needed, for the reasons 
illustrated below.

My CSV file is something like:

Bob, Jones, bjones at somewhere 
<javascript:open_compose_win('to=bjones%40somewhere&thismailbox=INBOX.sent-mail');>,,
John, Smith,jsmith at somewhere 
<javascript:open_compose_win('to=jsmith%40somewhere&thismailbox=INBOX.sent-mail');>,John 
Smith's address,
Dave, Peters,dpeters at somewhere 
<javascript:open_compose_win('to=dpeters%40somewhere&thismailbox=INBOX.sent-mail');>,,Dave's 
Phone number


If I import this file, I will not be able to import the extra detail on 
John Smith or
Dave Peters.  Looping round through all the lines in the CSV, 
identifying all the unique
fields, then presenting the first record, as well as the first of each 
record that
contains an extra field.

Hmmm.. managed to make that as clear as mud didn't I  - feel free to 
contact me directly
on kent@ the domain this email came from if you want a better explanation.

Regards,

Kent