At last we checked our lines of code and found the mistake.

Older versions of Powerbuilder in connection with SQL Anywhere 11 was more tolerant in using embedded SQL statements.

We had some calls of stored procedures which doesn´t return a result set. In some special cases (I don´t know which exactly) this call couses the crashes.

We added a simple "dummy result" to our SQL procedures and it´s running fine now.

Many thx for your support.

Try to update the Powerbuilder 2022 installation to latest build 3356 , As it has fixed few of such issues that we faced with earlier build. Without knowing the code behind the button it will be difficult for someone to help. 

If you are using third party external dlls then double check their definitions as sometimes new function is available and overflowing of long data type can occur if building 64 bits. 

Hi Chris,

thx for your quick reply.

I think it was a misunderstanding: Our app was running without any issue

but after migration to pb2022r3 we have these issues.

It crashes without any report besides the window error log.

I checked GDI and memory but there are no abnormalities.

It´s mysterious. The same function runs 10 times well and about 2 times wrong while processing always the same data.

I see only a connection to missing resources because the probability to crash increases with more open windows in the app.

Any idea how to find the error or does anyone has a work around?

Regards

Marco

Hi Marco;

   The crash in PBSHR.dll is where the PB runtime interfaces to the O/S SDK wise. This is normally where requests for resources are being made. So I suspect that the issue could be GDI or Memory related (as just a guess at the moment).

  It's hard to guess the reasons for the crashing where you stated that the app was working well initially. So I would approach this current issue with the old mechanics approach to such a problem ... "What's changed recently"?

Regards ... Chris