Still having same issue.....I did the following so  far

1. I made sure all datastores were destroyed
2. Change to different app and then changed back to app having issue
3. Tried pbtrace but couldn't find where the log file is placed from this.  Turned on debugger to see if there was a specific bit of code that was causing this.  Always hit the last line of code and after stepping off of that, IDE crashed
4. Created new Work PBL, had that In Lib List and did a full rebuild
5. Moved the Work PBL from 1st PBL in list to 2nd, behind PBL that has application and project objects.  Did full rebuid

I had varying degrees of success but none where the IDE crash stopped 100%.  In trying #4 & #5 above, it didn't crash on every closing of the app but crashed less frequently like after anywhere from 4 - 10 runs which at least kept me from pulling my hair out...but still an annoyance.

Unfortunately now, the crash is occurring again.  I have done adding the work PBL to Lib list and doing a full build.  Tried a number of other things to no avail.

I could put up with it as it doesn't happen in EXE but is a royal pain having to re-open PB every time I run the app.  Very time consuming.

In my case, the IDE freezes when closing the application since PB 2017 R1.  The windows (apart from the frame window) closes when Esc is pressed and the issue seems to happen most often than not when I close multiple windows in quick succession by pressing Esc.  And when only the frame window remains, the IDE freezes after I close the application.  All the windows have got the usual clean up in the close event.  I also added the DS.Reset, DS.dataobject ="" and Destroy DS suggested by Chris, but still the same issue.  Since the deployed application works ok, I just put up with the issue.

I'm sure you have checked, but 1) has the new WORK PBL been added to the Library List, and 2) then a FULL BUILD been done on the application before starting the app?

Olan

Thanks Chris!! What I had done to get to this issue is create a work PBL that is before all other PBLs in the app.  I created some new dwo's and have a current window that I moved to the work pbl to modify.  Once I run, go to this window and then close app,  I get the error.  All subsequent runs I get error even if I don't go as far as opening the window I'm modifying.

I tried taking the work PBL out of library list and still get error.  Now if I take the work PBL out, close PB and open PB back up, I don't get error (without work PBL).  So it is weird what is going on.

I need to go out and find documentation on /pbtrace as I very rarely used that...last time I did, I was following a document and couldn't get it to work.

On DB client driver, we use SQL Server.  Are you saying it could be a matter of just getting the most current driver and installing?

Hi David;

   When you execute the App from your PB IDE, the App is run as a "sub-task". If your App experiences any instability and in particular a crash. The MS-Window O/S escalates the problem to the main task which of course, is the IDE. Thus, if the sub-task crashes - the main task will likely as well. In 99% of the cases, its not a PB IDE stability issue - more in that it gets blamed for your App's demise and thus shutdown.

  The big question of course is why your App has this instability issue. If you build an EXE and run it .. does the App crash on close? If it does, does the System Error event fire so that the App can catch it? If not ... try running the EXE with a "/pbttrace" option and see if that point something peculiar happening at the point of closure.

Note: An unstable DB Client driver (or bad setting there) can also crash your PB App's prematurely as well.

Regards ... Chris