VB6 and Visio 2003

[Guest]

Folks:


While browsing through Visio 2003, I noticed a "VB6 Editor" component -
Tools >> Macro >> Visual Basic Editor.
I think this is a very useful combination and so I would like to get some
practice with the VB Editor and Visio 2003.
Any references/tutorials/examples deeply appreciated


* What is the purpose of including Visual Basic 6.3 within Visio 2003 ?
* VB6.3 Editor combines with Visio 2003 to accomplish what objectives ?





Thanks,
Jo.

 

[Chris Roth [ Visio MVP ]]

Some places to look:

John Marshall's (MVP) Site http://www.mvps.org/visio/VBA.htm
Microsoft Visio Developers
http://msdn.microsoft.com/office/understanding/visio/


And my quick Visio 101 in VBA:

To get hold of a shape, try this:

Dim visShp as visio.shape
set visShp = Visio.ActiveWindow.Selection(1) 'assuming a shape is selected

To see the text:

visShp.Text

To get at any property:

visShp.Cells("cellname").Formula ' or .ResultIU

Go to Window > Show ShapeSheet to see all the cells that a shape contains.

This should get you started!

--

Hope this helps,

Chris Roth
Visio MVP

 

[Guest]

Chris:

Thanks for your reply. Here are some additional questions that immediately
pop up.

I would like to use VB6/Visio combo to DISCOVER then DISPLAY various devices
on a network segment using Ping/ICMP/etc.

* How can I accomplish this goal ? Do I need to install a Visio
ActiveX component into my VB application ? Or do I have to use multiple
lines of VB code ?
* Is there a list of Visio ActiveX components to achieve various
objectives ?
* Where is your "quick Visio 101 in VBA" ?
* Can various Visio functions be launched from the Windows Command Prompt
? I am considering the possibility of running a batch file to DISCOVER &
DISPLAY various network segments ?
* Another way of ask the previous question is as follows: Does Visio
have a separate executable file for its DISCOVERY engine ?



Thanks,
John.

 

[Al Edlund]

understand it is VBA, not VB 6. There are differences.
al

 

[Al Edlund]

Short answer. the visio autodiscovery addon was discontinued in 2002, you
have to write your own. Network discovery algorithms come in many shapes;
from the semi-active reading of arp cache to the active ping of possible
addresses. Address sweeps tend to be discouraged because they look like
denial-of-service attacks.

basic visio programming can be found over here
http://msdn.microsoft.com/library/en-us/devref/HTML/DVS_01_Introduction__544.asp?frame=true

you should consider the v2003 sdk
http://msdn.microsoft.com/library/d...n-us/vissdk11/html/Doc_Summary_HV01083292.asp

some network code that can be adapted to work in visio is over at Randy
Birchs site
http://vbnet.mvps.org/

I personally use some activex controls from Dart
http://www.dart.com/powertcp/

finally saving the information (database) is also important and here is an
example of access/excel integration
http://msdn.microsoft.com/library/d...ml/decontheadoerrorobjecterrorscollection.asp

al

 

[Guest]

Al Edlund:


What are the differences between VBA (found in Visio 2002) and VB6 ?
My goal is to be able to use Visual Basic to accomplish various tasks
(network discovery, etc) in Visio
Any tutorials/references/links deeply appreciated.


Thanks,
John.

 

[Al Edlund]

I gave a couple of references in the previous append. this from msdn,
al

Visual Basic is the senior member of the family of Visual Basic products
that includes Visual Basic for Applications and Visual Basic, Scripting
Edition (VBScript). While most of the code that you write in Visual Basic
can be shared with applications written in Visual Basic for Applications or
VBScript, there are some exceptions.

Compatibility with Visual Basic for Applications
Visual Basic for Applications is a single, common application scripting
language and environment that users and developers can leverage across their
Windows desktop. Visual Basic for Applications is included in Microsoft
Office and other Microsoft applications. It is also licensed to other
software vendors and included in a wide range of products.

Visual Basic for Applications, contained in Vba6.dll, is the underlying
language engine for Visual Basic. This library contains all of the language
elements that are shared by Visual Basic for Applications and Visual Basic.
You can view the elements by selecting VBA from the Library listbox in the
Object Browser. Code written in Visual Basic for Applications is portable to
Visual Basic with the following limitations: Visual Basic for Applications
code that refers to application-specific elements (such as an Microsoft
Excel worksheet) may be ported, provided that they contain a fully qualified
reference and provided that the referenced application exists on the target
machine.

Elements specific to Visual Basic, such as forms and intrinsic controls, are
contained in the type library Vb6.olb (which is also visible in the Object
Browser). In general, code written in Visual Basic is portable to Visual
Basic for Applications as long as it doesnt reference these elements.

For More Information To learn more about Visual Basic for Applications,
visit the Microsoft Web site at http://www.microsoft.com.To learn more about
referencing objects, see "Creating a Reference to an Object" in "Programming
with Components." To learn more about native-code compilation, see
"Compiling Your Project to Native Code" in "More About Programming."