Path: csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!aioe.org!feeder.news-service.com!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: Lars Uffmann Newsgroups: comp.lang.basic.visual.misc Subject: Re: mscomctl.ocx and comctl32.ocx invoking third party executables? Date: Thu, 03 Feb 2011 17:40:34 +0100 Lines: 38 Message-ID: <8r040lF571U1@mid.dfncis.de> References: <8qvtngFppsU1@mid.dfncis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de Z9rnyRlwUGwBmpth+PMp2A7ZQujOo/uk2CUmyH0PRV/hi2b7LpDuZIoj1X Cancel-Lock: sha1:yYugcqIEa5RnDjkKtYB/IXfPvoc= User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) In-Reply-To: Xref: csiph.com comp.lang.basic.visual.misc:1876 GS wrote: > After serious thinking Lars Uffmann wrote : >> [Fullquote removed] > > First thing you need to understand is that ANY MS Office project that > uses either of these controls needs to have a reference set to them in > the VBE (Visual Basic Editor). I do not have the feeling that you fully understood my post. The MS Windows Common Controls are properly registered with the MS Office 2003 installation. And if they weren't, the project would be complaining about the ActiveX control being unknown/not found. But to be fair, you got me one step further: The component registration (reference creation) happens automatically, when the Common Control (e.g. ProgressBar) is inserted into the document. That is - if the object is not contained within the already referenced libraries/object files. Apparently this automatic referencing browses through available object files and finds some of my third-party software also. A call to these files then seems to invoke the installer. At least that is my current understanding of the problem. Still - why referencing a certain ActiveX where the object file is known would invoke other ActiveX object code is beyond me... > Also, the controls must be installed and properly registered on the > target machine the MSO project runs on. That means if your project will > be used on Vista OS or higher you'll have to distribute and register > these controls on that machine. This also means you'll have to develop > your project on a machine that has these OCXs properly installed. I don't understand what that has to do with the topic...? I am not trying to develop an office project, I am observing a strange/unwanted behaviour of an ActiveX control in office... And trying to find the cause. Cheers, Lars