J
Jeff Bennett
Is it possible to turn off Design Time support
for controls which are held inside Visio ActiveX control?
As I understand Visio reports itself as being in design
mode to controls embedded within the Visio ActiveX within
a compiled VB or VC application.
This means that end users of a compiled EXE application
which is itself based on Visio ActiveX will be able to
do things like right clicking on embedded controls and
have access to design time properties of those ActiveX controls.
More significantly it means that end-users of such
an application will need licenses for each ActiveX
embedded in the Visio application.
( Can someone verify that this is correct )
This would not be a problem for using these ActiveX
controls directly in the EXE, or within a standard frame
control. The problem only occurs because of the way
Visio ActiveX is acting ( as a development tool even
though it is held inside a compiled EXE ).
Is there a way to tell Visio ActiveX that it should
not present itself as a design time environment
and should not expose properties of the child controls
to end-users ? This is very important in order
to avoid royalties.
If replying in the forum, please also drop me a note
by e-mail to let me know to look here for answer.
( I don't frequent visio forums ).
Thank you very much.
* * Please include a copy of this note with your reply
Jeff Bennett
(e-mail address removed)
Bennet-Tec Information Systems, Inc
50 Jericho Tpk, Jericho, NY 11753
Phone 516 997 5596, Fax - 5597
WWW.Bennet-Tec.Com
RELIABLE Component Software
and Software Development Services
* TList/Pro * ALLText HT/Pro * MetaDraw *
====================== ======================
for controls which are held inside Visio ActiveX control?
As I understand Visio reports itself as being in design
mode to controls embedded within the Visio ActiveX within
a compiled VB or VC application.
This means that end users of a compiled EXE application
which is itself based on Visio ActiveX will be able to
do things like right clicking on embedded controls and
have access to design time properties of those ActiveX controls.
More significantly it means that end-users of such
an application will need licenses for each ActiveX
embedded in the Visio application.
( Can someone verify that this is correct )
This would not be a problem for using these ActiveX
controls directly in the EXE, or within a standard frame
control. The problem only occurs because of the way
Visio ActiveX is acting ( as a development tool even
though it is held inside a compiled EXE ).
Is there a way to tell Visio ActiveX that it should
not present itself as a design time environment
and should not expose properties of the child controls
to end-users ? This is very important in order
to avoid royalties.
If replying in the forum, please also drop me a note
by e-mail to let me know to look here for answer.
( I don't frequent visio forums ).
Thank you very much.
* * Please include a copy of this note with your reply
Jeff Bennett
(e-mail address removed)
Bennet-Tec Information Systems, Inc
50 Jericho Tpk, Jericho, NY 11753
Phone 516 997 5596, Fax - 5597
WWW.Bennet-Tec.Com
RELIABLE Component Software
and Software Development Services
* TList/Pro * ALLText HT/Pro * MetaDraw *
====================== ======================