Hi Guru
My program work in pb.70 as following statement, but upgrade to 2019 , it will be lead to program crushed, please advise
idw_report.SetSort(ls_keycolumn+" A")
idw_report.Sort()
Hi Guru
My program work in pb.70 as following statement, but upgrade to 2019 , it will be lead to program crushed, please advise
idw_report.SetSort(ls_keycolumn+" A")
idw_report.Sort()
Hi
I had a similar problem with PB12.5 and a PFC application just blewup when the user clicked on a column header to sort the DW. I did a lot of work with SAP on it to debug the problem, providing memory dumps etc. From their analysis they came back and said that the DW memory was corrupted somehow. Nothing to do with the PB code just a combination of DW design, data and the wind being in the wrong direction! (I added that last bit)
From what you said it does not crash in all cases, so I would recreate the datawindows that are a problem and see if it goes away :)
Hope that helps
David
In addition to what Andreas said, you just say the app crashed. Was there a message? Is it crashing in the IDE or EXE or both? Going from PB7 to 2019 you are moving to unicode is also something to consider. Have you done a Full Build on the code? Are you using any frameworks such as PFC? If pfc, did you also migrate to the newest version of the pfc? Did you check to make sure idw_report is not null? Hopefully the try/catch will trap the error. One client I had, we were getting multiple errors like this after converting from PB12 to 2017, but once we did a full build on the code, they went away.
Good luck,
Kevin
Hi.
You provide little information. This particular commands cannot be the cause of your crash. As from PB 7 to PB 2019 there are changes in the order events are triggered, I would try to debug and see if idw_report is:
Also, I would put
idw_report.SetSort(ls_keycolumn+" A")
idw_report.Sort()
in a try catch block and would check if an error throws...
Andreas.