I have build an application in Powerbuilder 6.5 that uses 2 OCX
controls. One of them is the GanttOCX from AddSoft, the other one is
home-made. Both OCX controls are working fine when running the
appliction from within the PB 6.5 development environment, but if I run
the executable and try to open the windows containing the controls the
executable is crashing and causing a Access Violation. This happens with
both the controls. 

Some Additional information: The OCX controls are created as a visual
ole user object and this ole user object is placed on a window.

If you have any ideas what is causing the application to crash, please
let me know.

Thanks, Maurice



~~~~~~~~~~~~~~~~~~~~~~~~~~
Maurice R. van SOEST                     
soest@nc3a.nato.int

NATO C3 Agency - The Hague
THE NETHERLANDS
http://www.nc3a.nato.int

Do the registry entries for the OCX's have fully qualified paths to their
files?

Carson

----------------------------------------------------------------------------
Carson Hager                          Dynamic Data Solutions
Team Powersoft                      http://www.dyn-data.com
MS Certified Professional
chager@dyn-data.com


         ********  Are You Ready for the Web  ********
                          www.jumpstart98.com


Maurice R. van Soest wrote in message <3613B025.5AB47479@nc3a.nato.int>...
>I have build an application in Powerbuilder 6.5 that uses 2 OCX
>controls. One of them is the GanttOCX from AddSoft, the other one is
>home-made. Both OCX controls are working fine when running the
>appliction from within the PB 6.5 development environment, but if I run
>the executable and try to open the windows containing the controls the
>executable is crashing and causing a Access Violation. This happens with
>both the controls.
>
>Some Additional information: The OCX controls are created as a visual
>ole user object and this ole user object is placed on a window.
>
>If you have any ideas what is causing the application to crash, please
>let me know.
>
>Thanks, Maurice
>
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~
>Maurice R. van SOEST
>soest@nc3a.nato.int
>
>NATO C3 Agency - The Hague
>THE NETHERLANDS
>http://www.nc3a.nato.int

The OCX's are fully registered with their right paths.

Even more, our homemade OCX is being used in VB, VC++ and Access
applications successfully, however it's all Microsoft.

In the meantime I did some testing and have created a window on which I
put the the GanttOCX directly (without any inheritance or whatsoever).
If I now run this executable the window and OCX are opening just fine,
so the next step is to add some coding to fill the object with data.

Maurice


Carson Hager[TeamPS] wrote:
> 
> Do the registry entries for the OCX's have fully qualified paths to their
> files?
> 
> Carson
> 
> ----------------------------------------------------------------------------
> Carson Hager                          Dynamic Data Solutions
> Team Powersoft                      http://www.dyn-data.com
> MS Certified Professional
> chager@dyn-data.com
> 
>          ********  Are You Ready for the Web  ********
>                           www.jumpstart98.com
> 
> Maurice R. van Soest wrote in message <3613B025.5AB47479@nc3a.nato.int>...
> >I have build an application in Powerbuilder 6.5 that uses 2 OCX
> >controls. One of them is the GanttOCX from AddSoft, the other one is
> >home-made. Both OCX controls are working fine when running the
> >appliction from within the PB 6.5 development environment, but if I run
> >the executable and try to open the windows containing the controls the
> >executable is crashing and causing a Access Violation. This happens with
> >both the controls.
> >
> >Some Additional information: The OCX controls are created as a visual
> >ole user object and this ole user object is placed on a window.
> >
> >If you have any ideas what is causing the application to crash, please
> >let me know.
> >
> >Thanks, Maurice
> >
> >
> >
> >~~~~~~~~~~~~~~~~~~~~~~~~~~
> >Maurice R. van SOEST
> >soest@nc3a.nato.int
> >
> >NATO C3 Agency - The Hague
> >THE NETHERLANDS
> >http://www.nc3a.nato.int

-- 

~~~~~~~~~~~~~~~~~~~~~~~~~~
Maurice R. van SOEST                     
soest@nc3a.nato.int

NATO C3 Agency - The Hague
THE NETHERLANDS
http://www.nc3a.nato.int

--------------DF3F7C83CBEC23AA709E533B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Maurice:
Please keep us up to date on your progress.
It's interesting that it's working without inheritance......
Is this a PCode executable or MachineCode???
There have been some hard to reproduce errors in MachineCode
executables.
We generally recommend to stick with PCode unless
you really really need the gain that MCode will give you (and
then _measure_ the gain you get to make sure the long
rebuild times are worth the trouble).

Regards,
Reed Shilts
PowerBuilder Kernel Group
***Nothing I Say Is Official***


Maurice R. van Soest wrote:

> The OCX's are fully registered with their right paths.
>
> Even more, our homemade OCX is being used in VB, VC++ and Access
> applications successfully, however it's all Microsoft.
>
> In the meantime I did some testing and have created a window on which I
> put the the GanttOCX directly (without any inheritance or whatsoever).
> If I now run this executable the window and OCX are opening just fine,
> so the next step is to add some coding to fill the object with data.
>
> Maurice
>
> Carson Hager[TeamPS] wrote:
> >
> > Do the registry entries for the OCX's have fully qualified paths to their
> > files?
> >
> > Carson
> >
> > ----------------------------------------------------------------------------
> > Carson Hager                          Dynamic Data Solutions
> > Team Powersoft                      http://www.dyn-data.com
> > MS Certified Professional
> > chager@dyn-data.com
> >
> >          ********  Are You Ready for the Web  ********
> >                           www.jumpstart98.com
> >
> > Maurice R. van Soest wrote in message <3613B025.5AB47479@nc3a.nato.int>...
> > >I have build an application in Powerbuilder 6.5 that uses 2 OCX
> > >controls. One of them is the GanttOCX from AddSoft, the other one is
> > >home-made. Both OCX controls are working fine when running the
> > >appliction from within the PB 6.5 development environment, but if I run
> > >the executable and try to open the windows containing the controls the
> > >executable is crashing and causing a Access Violation. This happens with
> > >both the controls.
> > >
> > >Some Additional information: The OCX controls are created as a visual
> > >ole user object and this ole user object is placed on a window.
> > >
> > >If you have any ideas what is causing the application to crash, please
> > >let me know.
> > >
> > >Thanks, Maurice
> > >
>



--------------DF3F7C83CBEC23AA709E533B
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<HTML>
Maurice:
<BR>Please keep us up to date on your progress.
<BR>It's interesting that it's working without inheritance......
<BR>Is this a PCode executable or MachineCode???
<BR>There have been some hard to reproduce errors in MachineCode
<BR>executables.
<BR>We generally recommend to stick with PCode unless
<BR>you really really need the gain that MCode will give you (and
<BR>then _measure_ the gain you get to make sure the long
<BR>rebuild times are worth the trouble).

<P>Regards,
<BR>Reed Shilts
<BR>PowerBuilder Kernel Group
<BR>***Nothing I Say Is Official***
<BR>&nbsp;

<P>Maurice R. van Soest wrote:
<BLOCKQUOTE TYPE=CITE>The OCX's are fully registered with their right paths.

<P>Even more, our homemade OCX is being used in VB, VC++ and Access
<BR>applications successfully, however it's all Microsoft.

<P>In the meantime I did some testing and have created a window on which
I
<BR>put the the GanttOCX directly (without any inheritance or whatsoever).
<BR>If I now run this executable the window and OCX are opening just fine,
<BR>so the next step is to add some coding to fill the object with data.

<P>Maurice

<P>Carson Hager[TeamPS] wrote:
<BR>>
<BR>> Do the registry entries for the OCX's have fully qualified paths
to their
<BR>> files?
<BR>>
<BR>> Carson
<BR>>
<BR>> ----------------------------------------------------------------------------
<BR>> Carson Hager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Dynamic Data Solutions
<BR>> Team Powersoft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="http://www.dyn-data.com">http://www.dyn-data.com</A>
<BR>> MS Certified Professional
<BR>> chager@dyn-data.com
<BR>>
<BR>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ********&nbsp;
Are You Ready for the Web&nbsp; ********
<BR>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
www.jumpstart98.com
<BR>>
<BR>> Maurice R. van Soest wrote in message &lt;3613B025.5AB47479@nc3a.nato.int>...
<BR>> >I have build an application in Powerbuilder 6.5 that uses 2 OCX
<BR>> >controls. One of them is the GanttOCX from AddSoft, the other one
is
<BR>> >home-made. Both OCX controls are working fine when running the
<BR>> >appliction from within the PB 6.5 development environment, but if
I run
<BR>> >the executable and try to open the windows containing the controls
the
<BR>> >executable is crashing and causing a Access Violation. This happens
with
<BR>> >both the controls.
<BR>> >
<BR>> >Some Additional information: The OCX controls are created as a visual
<BR>> >ole user object and this ole user object is placed on a window.
<BR>> >
<BR>> >If you have any ideas what is causing the application to crash,
please
<BR>> >let me know.
<BR>> >
<BR>> >Thanks, Maurice
<BR>> >
<BR><A HREF="http://www.nc3a.nato.int"></A>&nbsp;</BLOCKQUOTE>
&nbsp;</HTML>

--------------DF3F7C83CBEC23AA709E533B--

Our exe is in MachineCode, because we need al the speed we can get (I
thought that was the idea of creating machinecode executables), but if
you tell me that it isn't always obvious, we might need to take a closer
look at that later. Anyhow, I have rebuilt the executable in PCode and
this seems to work much better. The initial test are looking promising.
No crashes until so far.

Thanks for your help.

Maurice van Soest.


BTW: Another thing you might be interested in: I have noticed that both
on Windows 95 and 98, PB 6.5 is less stable then on Windows NT 4.0. If I
run the same application within the development environment and opening
the windows with the OCX controls, PB 6.5 is crashing. This forced me to
upgrade a portable to Windows NT 4.0, which indeed did solve these
crashes.


Reed Shilts wrote:
> 
> Maurice:
> Please keep us up to date on your progress.
> It's interesting that it's working without inheritance......
> Is this a PCode executable or MachineCode???
> There have been some hard to reproduce errors in MachineCode
> executables.
> We generally recommend to stick with PCode unless
> you really really need the gain that MCode will give you (and
> then _measure_ the gain you get to make sure the long
> rebuild times are worth the trouble).
> 
> Regards,
> Reed Shilts
> PowerBuilder Kernel Group
> ***Nothing I Say Is Official***
> 
> 
> Maurice R. van Soest wrote:
> 
> > The OCX's are fully registered with their right paths.
> >
> > Even more, our homemade OCX is being used in VB, VC++ and Access
> > applications successfully, however it's all Microsoft.
> >
> > In the meantime I did some testing and have created a window on
> > which I
> > put the the GanttOCX directly (without any inheritance or
> > whatsoever).
> > If I now run this executable the window and OCX are opening just
> > fine,
> > so the next step is to add some coding to fill the object with data.
> >
> > Maurice
> >
> > Carson Hager[TeamPS] wrote:
> > >
> > > Do the registry entries for the OCX's have fully qualified paths
> > to their
> > > files?
> > >
> > > Carson
> > >
> > >
> > ----------------------------------------------------------------------------
> >
> > > Carson Hager                          Dynamic Data Solutions
> > > Team Powersoft                      http://www.dyn-data.com
> > > MS Certified Professional
> > > chager@dyn-data.com
> > >
> > >          ********  Are You Ready for the Web  ********
> > >                           www.jumpstart98.com
> > >
> > > Maurice R. van Soest wrote in message
> > <3613B025.5AB47479@nc3a.nato.int>...
> > > >I have build an application in Powerbuilder 6.5 that uses 2 OCX
> > > >controls. One of them is the GanttOCX from AddSoft, the other one
> > is
> > > >home-made. Both OCX controls are working fine when running the
> > > >appliction from within the PB 6.5 development environment, but if
> > I run
> > > >the executable and try to open the windows containing the
> > controls the
> > > >executable is crashing and causing a Access Violation. This
> > happens with
> > > >both the controls.
> > > >
> > > >Some Additional information: The OCX controls are created as a
> > visual
> > > >ole user object and this ole user object is placed on a window.
> > > >
> > > >If you have any ideas what is causing the application to crash,
> > please
> > > >let me know.
> > > >
> > > >Thanks, Maurice
> > > >
> >
> 
> 

-- 

~~~~~~~~~~~~~~~~~~~~~~~~~~
Maurice R. van SOEST                     
soest@nc3a.nato.int

NATO C3 Agency - The Hague
THE NETHERLANDS
http://www.nc3a.nato.int