I dont have a ready solution for ur problem. But it seems to me to be a
memory problem. Look at it: Kernel32.dll is having the problem.
Kernel32.dll is responsible in Windows for resources and memory. I think
maybe combining the dws in the composite dw the no of rows requires more
memory than required and maybe the virtual memory settings are not perfect
or not sufficient enough. U C.. NT has a much better and sophisticated way
of managing both these: the resources and memory than any other MS
software. And 16 bit exe's are also quite vulnerable to all these. PS
recognizes them too.
So... if u have a solution other than wot seems to me, please mail me the
solution. I am very eager to know.
Best of Luck
IBM Solution Developer
E-Mail: email@example.com, firstname.lastname@example.org
ESSO (Schweiz) <email@example.com> wrote in article
> Hi PB'ers
> We have a strange problem when trying to print a datawindow with a
> nested datawindow.
> Printing from a 32 bit (interpreted or compiled) application under
> windows 95, the application crashes in the Kernel32.dll.
> If the same application is run under NT3.51 the there are no problems.
> The same goes if the same application is made as a 16 bit application.
> (running under NT, Win3 or Win95).
> We have the same problem in more than one application with different
> datawindows being printed, but the application doesn't crash every time
> a datawindow with a nested datawindow is printed.
> We are using Powerbuilder 5.0.03.
> Preben Hansen