It would certainly be possible to parse a multi-item vCard file into multiple vCard files using FileSystemObject or the usual cast of text parsing functions. Then you can import them with Outlook 2007's nifty new Namespace.OpenSharedItem method.

Perhaps a little weekend VBA project?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Mike" wrote in message ...
I hadn't realized how well multi-item vCal importing worked until
yesterday - very nice! I guess I was also wondering if there was any
workaround for the limitations of vCard support - perhaps through code?
Thanks,

Mike

"Sue Mosher [MVP-Outlook]" wrote in message
...
Such "why?" questions are largely rhetorical unless you can corner a
Microsoft developer in an unusually talkative mood. This being a
peer-to-peer forum, you won't find them here. It's not hard to guess,
though, that multiple-contact vCard support simply wasn't high enough on the
to-do list to get the resources this time around, given all the other design
priorities.

Once people see how well multi-event iCalendar support works in OL2007, I
imagine they'll be asking loudly for the same capability for contacts.


"Mike" wrote in message
...
Outlook 2007 (like previous versions of Outlook) still fails to properly
implement the vCard standard. In a VCF file with mulitple records,
Outlook
only imports the first one; even Outlook Express will import this kind of
VCF file correctly. On the flip side Outlook cannot properly create VCF
files from mulitple contacts; yes, there is the kludge to foward an an
email
with multiple contacts, but this does not create a single VCF file, and
requires numerous extra steps (and takes a LONG time for a large list). I
know there are tools to 'fix' this, but is there a reason Outlook still
fails to implement this standard correctly?

Mike