Hi All,
I am hoping that the community can point me in the right direction here to try and track down why a specific window in an application crashes consistently on an attempt to open.
Running under Windows 10 and built with PB2017 R3, Build 1858, the scenario is
Window opens and performs normally when run from the PB IDE.
Whan running executable from a Windows File folder, the window crashes consistently. I have run with /pbdebug and unfortunately there are no clues in there. The last lines of the pbdebug output are
Executing instruction at line 5
Executing instruction at line 6
Executing instruction at line 7
stack size changed during a routine call
End class function +CREATE for class W_MYWINDOW, lib entry W_MYWINDOW
and then nothing else. It appears to have finished the class function and then blown up.
Now, the strange thing is that if I shell out to dos or create a batch file to run the executable, the window opens and functions correctly, as it does when the Windows compatability troubelshooter is activated. Alas, these are not viable workarounds in our environment.
In an attempt to see if I could trap the runtime error, I added try catch to code code in several events and functions in the window and it's ancestor, but that made no difference.
Any advice, greatly appreciated.
Thanks
Davy
As well as looking into the path, which I am doing now, would a worthwhile approach be to use the PB2017 run time packager to get the necessary dlls etc and copy these to a new folder along with the .exe and .pbds. If I then ran the exe directly from this new folder would this guarantee that I am picking up the correct dlls etc?
If want to test, I'd suggest using a VM or another machine without PB installed. If all runs ok with the packaged DLLs, then you can be reasonably certain that there's another set of DLLs causing problems.