Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Setting Print.Preview crashes on 64-bit computers

2 posts in DataWindow Last posting was on 2010-02-04 18:01:16.0Z
Dan Cooperstock Posted on 2009-12-24 15:53:32.0Z
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Setting Print.Preview crashes on 64-bit computers
From: Dan Cooperstock <info@Software4NonProfits.com>
Organization: Software4NonProfits.com
Message-ID: <Xns9CEB6ECEC835FinfoSoftwareNonProfi@192.138.151.106>
User-Agent: Xnews/5.04.25
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 24 Dec 2009 07:53:32 -0800
X-Trace: forums-1-dub 1261670012 10.22.241.152 (24 Dec 2009 07:53:32 -0800)
X-Original-Trace: 24 Dec 2009 07:53:32 -0800, vip152.sybase.com
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:90485
Article PK: 410090

Some of my users with 64-bit computers (usually with Vista) are complaining
that sometimes (or often) when they go to run a report, the app hangs, with
a message from Windows like "This application has stopped working". When
they click OK on that message, the app dies.

This seems to happen both with DWs that are forced by PB into print preview
mode (ones with nested reports, or composite reports) and with other ones,
at the point that my app turns on print preview mode with:

dw.Object.DataWindow.Print.Preview = "Yes"

If you reboot your computer after that problem, come back to the app, and
run the same report, it's fine! (Which suggests to me it's a PB bug, not
mine.)

Does anyone else have any similar experience? This is in PB 11.5.1, but I
had the same problem in PB 10.2. I've searched the newsgroup, but nobody
else has reported it.

---------------------------
Dan Cooperstock
DONATION web site: http://www.Software4Nonprofits.com
DONATION Support forums: http://forums.Software4Nonprofits.com
Email: mailto:info@Software4Nonprofits.com
Phone: 416-423-7722


Dan Cooperstock Posted on 2010-02-04 18:01:16.0Z
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Setting Print.Preview crashes on 64-bit computers
From: Dan Cooperstock <info@Software4NonProfits.com>
References: <Xns9CEB6ECEC835FinfoSoftwareNonProfi@192.138.151.106>
Organization: Software4NonProfits.com
Message-ID: <Xns9D1584779A539infoSoftwareNonProfi@192.138.151.106>
User-Agent: Xnews/5.04.25
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 4 Feb 2010 10:01:16 -0800
X-Trace: forums-1-dub 1265306476 10.22.241.152 (4 Feb 2010 10:01:16 -0800)
X-Original-Trace: 4 Feb 2010 10:01:16 -0800, vip152.sybase.com
Lines: 50
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:90718
Article PK: 410323

Dan Cooperstock <info@Software4NonProfits.com> wrote in
news:Xns9CEB6ECEC835FinfoSoftwareNonProfi@192.138.151.106:

> Some of my users with 64-bit computers (usually with Vista) are
> complaining that sometimes (or often) when they go to run a report,
> the app hangs, with a message from Windows like "This application has
> stopped working". When they click OK on that message, the app dies.
>
> This seems to happen both with DWs that are forced by PB into print
> preview mode (ones with nested reports, or composite reports) and with
> other ones, at the point that my app turns on print preview mode with:
>
> dw.Object.DataWindow.Print.Preview = "Yes"
>
> If you reboot your computer after that problem, come back to the app,
> and run the same report, it's fine! (Which suggests to me it's a PB
> bug, not mine.)
>
> Does anyone else have any similar experience? This is in PB 11.5.1,
> but I had the same problem in PB 10.2. I've searched the newsgroup,
> but nobody else has reported it.

OK, I think I have finally solved this problem, based on some comments in
another thread I started (asked in what situations you can get
"Appname.exe has stopped working" without the SystemError event being
triggered). Someone explained that meant it was a GPF. One reason you can
get GPFs is from "DLL hell", i.e. DLL incompatabilities.

I reviewed the Windows DLLs I was installing with my installer, which I
had based on the PB documentation. I found that I was always installing
GdiPlus.dll into the application folder, although when I re-read the PB
docs again carefully, I saw it was only required for Windows 2000. Since
PrintPreview is a graphical issue, I thought this might be the culprit.

On Vista or Windows 7 (where I was having this problem), GdiPlus.dll is
already present, so I was causing a conflict with the official Windows
version, by installing this earlier version that PB supplies in its C:
\Program Files\Sybase\Shared\PowerBuilder folder.

I'm not absolutely positive removing GdiPlus.dll from my application
folder on Windows Vista or 7 is a full solution to this problem, but so
far, it seems like it might be. (Since I've never been able to reproduce
the problem on my PCs, I'm depending on reports from clients to be sure.)

---------------------------
Dan Cooperstock
DONATION web site: http://www.Software4Nonprofits.com
DONATION Support forums: http://forums.Software4Nonprofits.com
Email: mailto:info@Software4Nonprofits.com
Phone: 416-423-7722