T
Thomas Rosted
Hi
I created an Office add-in in VB6. This add-in instantiates the forms
by calling an ActiveX exe with a minifest file to get XP styles and
being able to reference .net 2 (Word seems to reference 1.1 on some
machines, and only one version can be loaded at a time).
This works fine, the forms get styled and .net 2.0 can be referenced,
since the add-in is now effectively running as a seperate process. This
however also means that it no longer can be garantied that the forms
stay on top of the Office application, as that is no longer the owner,
since the add-in is in a different process.
Have anyone got any suggestions as to how I can solve this problem?
I've tried using various win32 api calls e.g. to always put the forms
on top, to set the office application as parent, but none of that works
correctly.
Best regards
Thomas Rosted
Traen Informationssystemer A/S
I created an Office add-in in VB6. This add-in instantiates the forms
by calling an ActiveX exe with a minifest file to get XP styles and
being able to reference .net 2 (Word seems to reference 1.1 on some
machines, and only one version can be loaded at a time).
This works fine, the forms get styled and .net 2.0 can be referenced,
since the add-in is now effectively running as a seperate process. This
however also means that it no longer can be garantied that the forms
stay on top of the Office application, as that is no longer the owner,
since the add-in is in a different process.
Have anyone got any suggestions as to how I can solve this problem?
I've tried using various win32 api calls e.g. to always put the forms
on top, to set the office application as parent, but none of that works
correctly.
Best regards
Thomas Rosted
Traen Informationssystemer A/S