Very weird problem with touchscreen monitor
DanTheMan
Application developed using Powerbuilder 10.2
Database ASA 9.02
Running on a Windows Vista 64bit
With a touchscreen monitor.
As a matter of fact the computer is a HP IQ804 which is an all-in-one
desktop PC with a touchscreen.
Issue:
The application is just crashing with no apparent reason. We have the
same application running on 64 bit machines. Vista machines and
Windows 7 machines without a problem. The only thing we could find on
that machine that is different from the others is the touchscreen.
We tried re-installing windows vista on the computer from scratch and
then just install our application with nothing else to make sure no
other software was causing the problem. We get the same issue. It's
not a standard powerbuilder crash with an object, event name and line
number. It's just a windows crash (GPF) and the module where it crash
differs so much it makes our head spinning. The modules range from
PBSHR100.dll to OLE32.dll and even KERNEL32.dll.
We thought we had pinpointed the problem to things like the
doubleclicked even (which our application uses a lot) but we found out
that the application is even crashing if we don't even touch it. Just
lauch it and leave it be will eventually cause it to crash. The only
thing we have running in the background in a timer event is a retrieve
of a datawindow (this is not rocket science).
We had another customer experiencing the same thing with a touchscreen
and just by changing to a regular monitor, the problem went away.
The problem with the HP IQ804 is that the hardware is IN the monitor
(think of it like an IMac). So the user cannot just change monitor
without changing the entire PC.
What in the touchscreen monitor or drivers could be causing our
software to crash? We'd like to find out why it does that. From what i
have read, we don't need anything special in Powerbuilder applications
to provide for touchscreens other than making the controls a bit
bigger. We're really puzzled.
We do have a licensed version of Powerbuilder 11 that we are planning
to migrate too in the future. Would it be worth the try to migrate the
application and beta test it on that computer and see if it takes care
of the touchscreen problems?