C
Chris
I'm using a standalone EXE in VB6 (SP5) to add master shapes to a Visio file
using the COM interface via Visio 2003 (SP1). I frequently get random
exceptions in the code and this also happens when executing code that
doesn't involve any Visio components. The problems even happens after I've
rebooted my computer. I also explicitly destroy objects references.
It also randomly causes strange behaviour such as:
A) Never leaving a FOR EACH [Object] IN Collection loop. (Items definitely
aren't being added while the loop takes place!!!)
B) Causing an error "Variable uses an automation type not supported in VB"
when attempting to access a particular collection item. This includes using
TypeName, IsObject etc. The collection items are of the same class. Other
items are OK.
Has anyone encountered similar problems? Is there anything I can do to fix
it?
using the COM interface via Visio 2003 (SP1). I frequently get random
exceptions in the code and this also happens when executing code that
doesn't involve any Visio components. The problems even happens after I've
rebooted my computer. I also explicitly destroy objects references.
It also randomly causes strange behaviour such as:
A) Never leaving a FOR EACH [Object] IN Collection loop. (Items definitely
aren't being added while the loop takes place!!!)
B) Causing an error "Variable uses an automation type not supported in VB"
when attempting to access a particular collection item. This includes using
TypeName, IsObject etc. The collection items are of the same class. Other
items are OK.
Has anyone encountered similar problems? Is there anything I can do to fix
it?