Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

problems using OLE Automation and ActiveX in PB 6

33 views
Skip to first unread message

Yakov Soblev

unread,
Nov 25, 1997, 3:00:00 AM11/25/97
to

Do you know any easy way to test it?
I 've got the right path in my .reg file and .tld file.
Those files have been generated with PowerBuilder 6.0
I've checked the .reg file though the editor. It looks OK.
The problem is - I can't access it through TCP/IP - using NT4.0 server, and
VB Script and ActiveX page.
I thought - that OLE automation object can be loaded same way as ActiveX
object. They are both based on COM. may be I am wrong.
Do you know of any easy way to test it?

Mike Everett <mic...@dialnet.net> wrote in article
<WKPn5J9...@forums.powersoft.com>...
> Sounds like you might need to modify it's reg file for it's location.
There
> are two entries in it that set the path to the DLL - you can't miss them.
>
> BTW once you do that just merge it with the registry. You don't need the
> regsvr32.exe program. If you want to automate that step I recommend
> InstallShield (a version of which is supposed to be included with the
final
> release of PowerBuilder)
>
> me
>
>
> Yakov Soblev wrote in message <01bceee9$d752a6c0$63859f96@dunt1857>...
> >We are writing a PowerBuilder application that can be used as OLE
Runtime
> >Automation Server.
> >We are using PowerBuilder 6.0 beta 3.
> >
> >We've built a 32-bit .pbd and made it a DLL ( OLE server )
> >We've used PowerBuilder sample program PBGENREG.PBL to generate .reg and
> >tlb (type library) files.
> >We've installed PowerBuilder deployment on Windows NT 4.0 server and
tried
> >to register
> >it with the system using "regsvr32.exe" program.
> >
> >We are getting an eror message:
> >
> >"C:\MyOLEServer.dll was loaded, but the DllRegisterServer entry point
was
> >not found.
> >DllRegisterServer may not be exported, or corrupted version is in
> >memory..."
> >
> >DllRegisterServer() registers DLL type library with the system and
should
> >be generated by PowerBuilder.
> >
> >To be an ActiveX control , our DLL must be a COM object, export
> >DLLRegisterServer and DLLUnRegisterServer.
> >
> >// C++ code for that function
> >STDAPI DllRegisterServer( void )
> >{
> > AFX_MANAGE_STATE(_afxModuleAddrThis);
> >
> > // Registers the type library with the Windows registration database
> > // and allows the type library to be used by other containers that
are
> >OLE-control aware. // This function updates the registry
> >with the type library name and its location
> > // on the system.
> > if ( ! AfxOleRegisterTypeLib ( AfxGetInstanceHandle( ), _tlid ) )
> > return ResultFromScode( SELFREG_E_TYPELIB );
> >
> > AfxOleRegisterTypeLib ( AfxGetInstanceHandle(), _tlid, _T(
> >"MyOLEServer.tlb" ) )
> >
> > if ( ! COleObjectFactoryEx :: UpdateRegistryAll ( TRUE ) )
> > return ResultFromScode( SELFREG_E_CLASS );
> >
> > return NOERROR;
> >}
> >
> >Is there an option in PowerBuilder 5.0.3 or PowerBuilder 6 that adds
> >DllRegisterServer function to generated by PowerBuilder OLE server DLL?
> >Is there a utility from PowerSoft that solves that problem?
> >What other options do we have to make OLE Server (ActiveX control) to
work?
> >
> >I can see my OLE Automation object with "OLE Viewer".
> >
> >But when I tried to access this OLE Automation using ActiveX Server Page
> >and VBScript - VBScript function was unable to create this object.
> >Isn't PowerBuilder 6 should be able to create ActiveX?
> >
> >
> >
>
>
>

0 new messages