I would second what Tom said, and also point out that your
App is going to take a performance hit if you go the Late
Binding route. The generally accepted method, as Tom said,
is to develop on a PC with the earliest version of Outlook
you want to support.
Virtual PC will certainly work; you will still need to
have Outlook 2000 installed within the virtual machine you
are doing the development from. In other words, if you go
the Virtual PC route, you can have Outlook 2002 on your
PC, but must install Outlook 2000 and VB/Visual Studio
(whichever you're using) installed into a Virtual Machine,
& do your development in that Virtual Machine.
My guess is, this is not what you're looking for - you
will see slower performance in the Virtual Machine unless
you've really got a monster of a PC with tons of RAM.
-Andrew
============================================
-----Original Message-----
I've been building an Outlook COM object and found that
the only way to get it to run on Office 2000 & 2002 was to
have Office 2000 on the devlopment machine. Is there
anyway to have Office 2002 on the development machine but
still make a COM object that can run on Office 2000
(Outlook)?