I got it to work by creating my .txt file manually and then
running through the Flowchart wizard. When I run it I get
the flowchart correctly but it tells me I have 13 errors,
one for each link. I used numeric values for the Shape Name
as this is the JobID from my Access table. Here is my file:
Template,"Basic Flowchart.VST"
Master,,"Process","Basic Flowchart Shapes.VSS"
Shape,"508122","Process","AGRFPDAY CM7MM1A (NOOP010)"
Shape,"508123","Process","AGRFPDAY CM7MM1A (CPU 020)"
Shape,"508124","Process","AGRFPDAY CM7MM1B (CPU 025)"
Shape,"508125","Process","AGRFPDAY CM7MM1C (CPU 040)"
Shape,"508126","Process","AGRFPDAY1A CM7DBMMV (CPU 002)"
Shape,"508127","Process","AGRFPDAY1A CM7DBMM0 (CPU 010)"
Shape,"508128","Process","AGRFPDAY1B CM7DBMMX (CPU 002)"
Shape,"508131","Process","AGRFPWEK CM7MM2C (CPU 085)"
Shape,"510591","Process","MMNOOP CM7MM (NOOP002)"
Shape,"510592","Process","MMRQLOAD CM7MM9A (CPU 005)"
Shape,"510610","Process","MMRQ9I CM7MM9I (CPU 010)"
Shape,"510612","Process","MMRQ9JB CM7MM9J (CPU 010)"
Link,"Mylink1","Connector","","508128","508122"
Link,"Mylink2","Connector","","508122","508123"
Link,"Mylink3","Connector","","508122","508124"
Link,"Mylink4","Connector","","508123","508125"
Link,"Mylink5","Connector","","508126","508127"
Link,"Mylink6","Connector","","508127","508128"
Link,"Mylink7","Connector","","508125","508131"
Link,"Mylink8","Connector","","508124","508131"
Link,"Mylink9","Connector","","508125","510591"
Link,"Mylink10","Connector","","508124","510591"
Link,"Mylink11","Connector","","508125","510592"
Link,"Mylink12","Connector","","508125","510610"
Link,"Mylink13","Connector","","508125","510612"
Now I will create the .txt file in my Access program and
then start Visio and create the Flowchart without any
manual intervention. This should be fun!!!
Quote:
>-----Original Message-----
>Tony:
>Just in case you missed this, I mentioned the *Flow chart*
wizard, and you
>are talking about having tried the *Org Chart* wizard,
which is indeed
>hierarchical.
>If Flowchart Wiz doesn't do what you want, then your task
basically
>involves:
>a) Iterate through the records in your database (use
either DAO or ADO, just
Quote:
>like in Access -- in fact you can write this in Access if
you want).
>b) Use the data to drop shapes on a Visio page
>c) Use the parent-child data to drop and glue Visio
connector shapes
>All of this is straightforward Visio VBA stuff -- you can
get a good run at
>it reading Developing Visio Solutions (online in the msdn
library
>documentation tree under Office Solutions Development).
Also available as a
>book.
>The hard part, however is figuring out the heuristics you
want for
>distributing the shapes on a page. This is not hard
programming, just hard
Quote:
>thinking :-) You can get some assistance by using
connectors consistently,
Quote:
>setting their routing style and then asking the
LayoutShapes function to do
Quote:
>it for you -- but mileage varies as to how desirable the
result. Try it
>with some manually placed shapes first to get an idea of
how various
>parameters affect this function (details in Visio Help)
>Graham
>--------------------------------------------
>Graham Wideman
>MS MVP for Visio
>Books:
>Visio 2000 Developer's Survival Guide
>Visio 2002 Developer's Survival Pack (with Tools)
>.... and resources for programmable diagramming at:
>http://www.diagramantics.com
>--------------------------------------------
>Unoffical Visio FAQ:
>http://www.diagramantics.com/diagenvs/visio/faq/index.htm
>(Remove the obvious to email me)
>---------------------------------------------
>> Yes I have already seen this. What I need to know is
what
>> is required in the .txt or .xls file so that Visio is
able
>> to draw my flowchart without any manual intervention
from
>> me or my users. I am able to write VBA code if needed as
I
>> have written many Excel and Access VBA macros. I
crerated a
>> file showing the parent child relationship and brought
into
>> the orgchart but this does not work as a child cannot
have
>> more than one parent
>> Thanks
>> Tony
>> >-----Original Message-----
>> >Tony:
>> >Have you already seen this in help?
>> >Create a text (.csv or.txt) data file from which to
>> generate a flowchart
>> >On the Tools menu, point to Macros, point to Flowchart,
>> and then click
>> >Import Flowchart Data Wizard.
>> >On the first wizard page, click Next.
>> >On the second wizard page, click Enter data in a new
text
>> file, and then
>> >click Next.
>> >On the third page, do one of the following:
>> >Click Next if your flowchart will use the Basic
Flowchart
>> template.
>> >Click Use a Custom Template if you want to use shapes
from
>> a different
>> >flowchart template. Click Browse to locate the
template,
>> click Open, and
>> >then click Next.
>> >On the fourth wizard page, enter a name for the new
data
>> file. Click the
>> >browse button and specify a location for the new file.
>> Click Save and then
>> >click Next.
>> >A text file opens that includes instructions for
setting
>> up the data file.
>> >Read the instructions, and then type your data in the
text
>> file. In the text
>> >file, on the File menu, click Save, and then click
Exit.
>> >In Microsoft Visio, on the final wizard page, click
>> Finish.
>> >--
>> >--------------------------------------------
>> >Graham Wideman
>> >MS MVP for Visio
>> >Books:
>> >Visio 2000 Developer's Survival Guide
>> >Visio 2002 Developer's Survival Pack (with Tools)
>> >.... and resources for programmable diagramming at:
>> >http://www.diagramantics.com
>> >--------------------------------------------
>> >Unoffical Visio FAQ:
>http://www.diagramantics.com/diagenvs/visio/faq/index.htm
>> >(Remove the obvious to email me)
>> >---------------------------------------------
>> >> I have developed an access database that contains the
>> >> scheduling information of our mainframe applications
>> >> (Predecessors and Successors). what I am trying to do
is
>> >> find out what data Visio needs to draw a flowchart of
>> the
>> >> jobs using parent/child. I tried with Organization
chart
>> >> but this does not permit multiple parents to a child.
I
>> >> need to know what data has to be included in either a
>> table
>> >> or text file that Visio can use to draw my flow
chart.
>> >.
>.