folks,

My app is written in VB and makes use of the Visio Object model to create
Visio Diagrams. We develop on workstations using Visio 2002. About half of
our users are using Visio 2000 and would rather not upgrade to Visio 2002.

We are quite pleased with the level of compatibility. However there are some
differences that we have hit upon recently. Mostly in PageSetup,
PrinterSetup options. We have to access these features to work around other
differences in  Print Preview behavoiur between the 2 versions.

Questions are :

What is the recommended development strategy -- to support Visio 2000 &
Visio 2002 (and presumably upcoming newer versions). ? DEvelop using 2000
and deploy against 2002 might be one but we would rather not unless forced.

Appears that some constants have changed their names. For instance visHoriz
and visVert for Guide types. Of course we hope that such tweaking of names
would stop.

Insights by other developers deeply appreciated.

regards

srini

Every release of Visio adds hundreds of new items to Visio's API.  However,
you need to program for the earliest version of Visio that you wish to be
compatible with.  Each API entry in the Developer Reference should include
the version when it was first introduced.  This will let you determine what
will not work in older releases.

Generally Visio tries to ensure that add-ons written for previous versions
of Visio will continue to function properly, but there always seem to be a
couple of exceptions.  When you encounter one of these issues, please notify
us so that we can keep our knowledge base up to date.

--
Mark Nelson
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.