I am using this to create a GUID.

OLEObject  pbobj
string            ls_guid
long              ll_rc
pbobj = create OLEObject
pbobj.connectToNewObject("Powerbuilder.Application")
ll_rc = pbobj.generateguid(ref ls_guid)

When I run locally it works, I get a GUID every time.  If I build my
application and deploy it I don't get the GUID.

Is there any powerbuilder dll that I need to include in my deployment for
this to work.  The rpcrt4.dll is in the path in the C:\WINNT\System32
directory.  When deployed the application is running through citrix would
this cause an issue?

Is there a way to get the Powerbuilder Application OLE object on a machine
without installing Powerbuilderl?

"Rich Catlett" <rc2581@sbc.com> wrote in message
news:42039ac2$1@forums-1-dub...
> I am using this to create a GUID.
>
> OLEObject  pbobj
> string            ls_guid
> long              ll_rc
> pbobj = create OLEObject
> pbobj.connectToNewObject("Powerbuilder.Application")
> ll_rc = pbobj.generateguid(ref ls_guid)
>
> When I run locally it works, I get a GUID every time.  If I build my
> application and deploy it I don't get the GUID.
>
> Is there any powerbuilder dll that I need to include in my deployment for
> this to work.  The rpcrt4.dll is in the path in the C:\WINNT\System32
> directory.  When deployed the application is running through citrix would
> this cause an issue?
>
>

You don't need to install the entire IDE, just the PB runtime files (PBVM, PBRTE, PBDWE, and so on).  If you're on PB9 
or later, there's a utility called PBPACK90.EXE (PBPACK100.EXE for PB10) that packages up all the client-side DLLs and 
stuff into a Microsoft Installer file (.MSI) which you can distribute as part of your application install.

-- 
Paul Horan[TeamSybase]

"Rich Catlett" <rc2581@sbc.com> wrote in message news:4207e878$1@forums-2-dub...
> Is there a way to get the Powerbuilder Application OLE object on a machine
> without installing Powerbuilderl?
>

We already include pbdwe.dll, pbodb.dll, pbrtc.dll and pbvm.dll in out
deployment.  Is there another dll that we should include to make the
following call work?

pbobj = create OLEObject
ll_rc = pbobj.connectToNewObject("Powerbuilder.Application")

This works locally, but not when our applicationis deployed to the servers.

"Paul Horan[TeamSybase]" <paulhATvcisolutionsDOTcom> wrote in message
news:4208d354$1@forums-2-dub...
> You don't need to install the entire IDE, just the PB runtime files (PBVM,
PBRTE, PBDWE, and so on).  If you're on PB9
> or later, there's a utility called PBPACK90.EXE (PBPACK100.EXE for PB10)
that packages up all the client-side DLLs and
> stuff into a Microsoft Installer file (.MSI) which you can distribute as
part of your application install.
>
> -- 
> Paul Horan[TeamSybase]
>
> "Rich Catlett" <rc2581@sbc.com> wrote in message
news:4207e878$1@forums-2-dub...
> > Is there a way to get the Powerbuilder Application OLE object on a
machine
> > without installing Powerbuilderl?
> >
>
>

"Rich Catlett" <rc2581@sbc.com> wrote in message news:4208dfcf$1@forums-1-dub...
> We already include pbdwe.dll, pbodb.dll, pbrtc.dll and pbvm.dll in out
> deployment.  Is there another dll that we should include to make the
> following call work?
>
> pbobj = create OLEObject
> ll_rc = pbobj.connectToNewObject("Powerbuilder.Application")
>
> This works locally, but not when our applicationis deployed to the servers.
>


Define "deployed to the servers"...   Are you saying that your clients run the applications from a shared LAN drive?  If 
so, are the PB runtimes on the server too, or just your .EXE/.PBD executable files?

For a PB application to use ConnecttoNewObject(), the COM class that's referenced (whether it's 
PowerBuilder.Application, or Excel.Application, or whatever) has got to be registered on the LOCAL WORKSTATION.  Now, 
you can register a DLL that lives out on a network share, but that registration has got to be in the local registry just 
the same.

On my machine, PowerBuilder.Application is registered to "C:\Program Files\Sybase\Shared\PBVM100.DLL".  If you don't 
want to install those PB runtimes locally, then just register the DLL from the LAN drive it's currently living in.

-- 
Paul Horan[TeamSybase]

We run our application from servers via citrix.  In order to deploy out
application we copy the pbd's, dll's and any extra runtime files need to the
servers.

We tried to register pbvm90.dll using the Regsvr32 E:\\<path to
dll>\pbvm90.dll

pbvm90.dll was loaded, but the DllRegisterServer entry point was not found.

pbvm90.dll may not be exported, or a corrupted version of Dllname may be in
memory. Consider using Pview to detect the file and remove it.

We tried severl different pbvm.dll's in different locations that we use to
run our application just fine, but they all returned the following error.

Any ideas?


"Paul Horan[TeamSybase]" <paulhATvcisolutionsDOTcom> wrote in message
news:42095112$1@forums-1-dub...
> "Rich Catlett" <rc2581@sbc.com> wrote in message
news:4208dfcf$1@forums-1-dub...
> > We already include pbdwe.dll, pbodb.dll, pbrtc.dll and pbvm.dll in out
> > deployment.  Is there another dll that we should include to make the
> > following call work?
> >
> > pbobj = create OLEObject
> > ll_rc = pbobj.connectToNewObject("Powerbuilder.Application")
> >
> > This works locally, but not when our applicationis deployed to the
servers.
> >
>
>
> Define "deployed to the servers"...   Are you saying that your clients run
the applications from a shared LAN drive?  If
> so, are the PB runtimes on the server too, or just your .EXE/.PBD
executable files?
>
> For a PB application to use ConnecttoNewObject(), the COM class that's
referenced (whether it's
> PowerBuilder.Application, or Excel.Application, or whatever) has got to be
registered on the LOCAL WORKSTATION.  Now,
> you can register a DLL that lives out on a network share, but that
registration has got to be in the local registry just
> the same.
>
> On my machine, PowerBuilder.Application is registered to "C:\Program
Files\Sybase\Shared\PBVM100.DLL".  If you don't
> want to install those PB runtimes locally, then just register the DLL from
the LAN drive it's currently living in.
>
> -- 
> Paul Horan[TeamSybase]
>
>

"Rich Catlett" <rc2581@sbc.com> wrote in message news:420a5c15$1@forums-1-dub...
> We run our application from servers via citrix.  In order to deploy out
> application we copy the pbd's, dll's and any extra runtime files need to the
> servers.
>
> We tried to register pbvm90.dll using the Regsvr32 E:\\<path to
> dll>\pbvm90.dll
>
> pbvm90.dll was loaded, but the DllRegisterServer entry point was not found.
>
> pbvm90.dll may not be exported, or a corrupted version of Dllname may be in
> memory. Consider using Pview to detect the file and remove it.
>
> We tried severl different pbvm.dll's in different locations that we use to
> run our application just fine, but they all returned the following error.
>
> Any ideas?
>
>


Look at the machine's PATH variable.  Try adding E:\<path to dll>  into the PATH and re-registering the DLL.

-- 
Paul Horan[TeamSybase]

We added pbvm90.dll to the system path, and we still get the error that is
mentioned below.  The dll isn't bad because we use to to run our
application, and we have tried it on different machines with different dlls.
We're stumped, is the pbvm90.dll the dll the allows powerbuilder to create
the "Powerbuilder Application" OLE object?  What can we do to get this to
work?  Any ideas?

"Paul Horan[TeamSybase]" <paulhATvcisolutionsDOTcom> wrote in message
news:420a8bf1$1@forums-1-dub...
> "Rich Catlett" <rc2581@sbc.com> wrote in message
news:420a5c15$1@forums-1-dub...
> > We run our application from servers via citrix.  In order to deploy out
> > application we copy the pbd's, dll's and any extra runtime files need to
the
> > servers.
> >
> > We tried to register pbvm90.dll using the Regsvr32 E:\\<path to
> > dll>\pbvm90.dll
> >
> > pbvm90.dll was loaded, but the DllRegisterServer entry point was not
found.
> >
> > pbvm90.dll may not be exported, or a corrupted version of Dllname may be
in
> > memory. Consider using Pview to detect the file and remove it.
> >
> > We tried severl different pbvm.dll's in different locations that we use
to
> > run our application just fine, but they all returned the following
error.
> >
> > Any ideas?
> >
> >
>
>
> Look at the machine's PATH variable.  Try adding E:\<path to dll>  into
the PATH and re-registering the DLL.
>
> -- 
> Paul Horan[TeamSybase]
>
>

"Rich Catlett" <rc2581@sbc.com> wrote in message news:420e4c43$1@forums-2-dub...
> We added pbvm90.dll to the system path, and we still get the error that is
> mentioned below.  The dll isn't bad because we use to to run our
> application, and we have tried it on different machines with different dlls.
> We're stumped, is the pbvm90.dll the dll the allows powerbuilder to create
> the "Powerbuilder Application" OLE object?  What can we do to get this to
> work?  Any ideas?
>

Yes - PBVM90.DLL "is" the DLL that creates "PowerBuilder.Application".  We've built an integration architecture around 
this approach, so I know it works well.

You don't add the DLL to the path - you add the FOLDER containing the DLL (and all the other DLLs) to the PATH.
i.e., not C:\Program Files\yourApp\pb9i32DK\pbvm90.dll;    but just: C:\Program Files\yourApp\pb9i32DK;   Then you run 
REGSVR32 <foldername>\PBVM90.DLL in a command window.

The COM registration process needs to be able to reference all the DLLs that the file being registered will also need. 
To see what I'm talking about, download a copy of DependencyWalker from www.sysinternals.com, and run that against 
PBVM90.DLL.  You'll see that it needs PBDWE90.DLL, PBRTE90.DLL, LIBJCC.DLL, and about 5 or 6 others (not including all 
the MS Windows stuff).   If REGSVR32 can't "see" those files as well, the registration fails, and your app can't 
instantiate the class on a machine where that registration hasn't happened.  It works on your machine because you 
installed the PB9 IDE, and ITS install routine does that registration for you.

Compare the registries on a "working" machine to one that doesn't.  Go to HKEY_CLASSES_ROOT, and search for 
'PowerBuilder.Application'.  On a "working" machine, you should find it in the ProgID key underneath a specific GUID. 
The InProcServer32 key under that same GUID will reference the folder containing PBVMnn.DLL.  I'll bet this isn't there 
on a non-working machine.  This registration step needs to become part of your app deployment process.

-- 
Paul Horan[TeamSybase]