Hi Craig,
I can't offer too much at this point with the problem of why this may be happening with that particular Workspace, but I wonder if you changed your settings to not open a Workspace upon starting the IDE if that will help you to continue trouble-shooting by switching Workspaces, per Chris' suggestion. Assuming the IDE is not so unstable that you can't access the menus, then click on Tools, System Options then go to the Workspaces tab and uncheck Reopen workspace on startup.
If it is so unstable such that you can't even access the menus to change this option before it crashes, then navigate to where your PB.INI file is located. This may depend upon where/ how you installed PowerBuilder but on my machine, for example, it's located in "C:\Users\Mark\AppData\Local\Appeon\PowerBuilder 19.0". Then locate the line "ReopenWorkspace=1" and change the 1 to a 0, then try and start PowerBuilder again. You could also leave the setting as 1 but change the line in the PB.INI file that points to the last open Workspace ("LastWorkspace=........") and change it to a known working Workspace.
From there hopefully you would be able to open another Workspace, or maybe the previous working version of the Workspace in question, and continue trouble-shooting. However, if you still have a problem with the IDE crashing without a Workspace even open, or a known working Workspace open, then I would consider re-installing PowerBuilder.
PS...before you try and open a known working Workspace I would recommend making backups first.
HTH...regards,
Mark
Thank you for the prompt response.
I have optimized all of the PBLs, done a full build and closed the IDE. it still stops working when I close it and it still hangs when I run the application from the IDE.
This is so strange. It was working fine for most of the day yesterday until I tried to run the application from it.
I get this situation in the extremely very odd time with my framework (which is very complex from the authoring perspective). Normally, it turns out to be some code that I added / changed that either is causing the runtime stability issue or more likely - caused an App crash that in turn had the IDE corrupt an object class and/or library. Since I normally make daily (at minimum) backups, 99.9% of the recovery was to restore the framework from my last good daily backup. I only backup too when the framework / PB App that I am testing is working 100%.
Another thing that has worked for me in the past in these rare stability cases, is to open the IDE's Object Browser., then select "Show Hierarchy" and then "Expand All". From there, perform a "Regenerate" from the TOP level ancestor. Make sure that you perform this action for all Menu, User Object and Window classes. Then perform a Full Build. That normally works for me 90+% of the time.
HTH
Thank you again for the reply. I will certainly look into both suggestions and let you know how things went. :-)
I really appreciate the help.