Using excel to make flowcharts

[Chris H.]

Good morning everyone,

I am using visio 2003 Standard edition to make flowcharts of different
processess of the applications we run order to maintain our payroll, billing,
etc. systems. My question is that I know in visio 2000, there was a built-in
converter from excel to visio flowcharts, where u could specify the type of
shape u wanted represented and how to connect them. However in 2003 I can't
seem to find that same feature, i did see the excel to org charts, but with
that one, it will only take the ord chart shapes, it won't let me specify
other shapes to use. Also i tried using the Database wizard, but whenever i
import it using the master shape, it only allows me to specify one same and
makes them all the same. So Is there anyway of duplicating the process from
2000 in the new 2003 or does anyone know how to use the Master_Shape field to
be able to use other shapes besides org chart shapes, for example like using
the basic flowchart shapes.?

Thanks for your time.

 

[Mark Nelson [MS]]

Visio 2003 does not include that flowchart wizard. There is a sample
application in the Visio SDK that illustrates generating a flowchart from
Excel (requires Visual Studio 2003 or later).

http://msdn.microsoft.com/library/d...n-us/vissdk11/html/Doc_Summary_HV01083292.asp

--
Mark Nelson
Office Graphics - Visio
Microsoft Corporation

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

 

[Chris H.]

Thanks, I downloaded the Visio SDK and it looks like that is the exact wizard
i need, the only problem is that the rest of my microsoft office suite is
only 2000, and thus it will not work with my excel 2000, is there anyway
around this?

 

[Mark Nelson [MS]]

I don't know whether the code depends on parts of the Excel API newer than
2000 or not. Perhaps there is a way to change a reference to use the Excel
type library for the version you have, but I would not know the steps.

--
Mark Nelson
Office Graphics - Visio
Microsoft Corporation

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

 

[Al Edlund]

In at least the .net scenario it is coded as office 11 in the references,
you can probably change it to reference what you're looking for.
al