From: Jeff Date: 2007-03-06T07:10:14+09:00 Subject: Re: Win32OLE trouble (custom ocx) > You're leading me toward the problem. That VBScript code does not work. > It actually gives the same error statement that win32ole gives! > > I went back and tried to re-create my VBScript code. I remembered I > used "ActiveX Control Pad" to test the VBScript method last year. > > This is code (embeded in and html doc and mostly generated by ActiveX > control pad) that works with my ocx. > > OCX test > > > > CLASSID="CLSID:884BD6BB-E4BA-4EEA-A632-D7A92541602F"> > > > > > > Any chance that the CLSID that works (884BD6BB-E4BA-4EEA-A632- D7A92541602F) is not registered correctly? Maybe QPTNT.QPTntCtrl.1 is not the right ProgID for that particular CLSID? I think you'll have to check the registry to be sure. Jeff softiesonrails.com