Exporting VCF
 

I've been sent a .vcf from a mac user. I am running Win XP with Outlook 2002.

The .vcf contains more than one contact, which I can see if I open in
notepad. However, I can't seem to export the data to Excel for example so
it's in a more usable format.

If I double click on the original .vcf I only have access/ or can only view
one card or set of data

Exporting VCF
 

ASBiss wrote:

I've been sent a .vcf from a mac user. I am running Win XP with
Outlook 2002.

The .vcf contains more than one contact, which I can see if I open in
notepad. However, I can't seem to export the data to Excel for
example so it's in a more usable format.

If I double click on the original .vcf I only have access/ or can
only view one card or set of data

Since a .vcf file is just a text file, edit it into multiple .vcf files, one
for each conact, and open them each in trun, saving them to your Contacts.
--
Brian Tillman

Exporting VCF
 

This doesn't really help - I can only see there are multiple contacts when I
open in notepad.

How do I edit into multiple .vcf files?

"Brian Tillman" wrote:

ASBiss wrote:

I've been sent a .vcf from a mac user. I am running Win XP with
Outlook 2002.

The .vcf contains more than one contact, which I can see if I open in
notepad. However, I can't seem to export the data to Excel for
example so it's in a more usable format.

If I double click on the original .vcf I only have access/ or can
only view one card or set of data

Since a .vcf file is just a text file, edit it into multiple .vcf files, one
for each conact, and open them each in trun, saving them to your Contacts.
--
Brian Tillman

Exporting VCF
 

ASBiss wrote:

This doesn't really help - I can only see there are multiple contacts
when I open in notepad.

How do I edit into multiple .vcf files?

Are there multiple BEGIN:VCARD and END:VCARD statements? If so, it should
be fairly easy to cut and paste each segment into another .vfc file.
Otherwise, you can cut and paste from one N: statement to the next, adding
your own BEGIN and END statements.
--
Brian Tillman