SQLTalk 12.0.1 Problem with Execution Plan

[phil@informasys.com]

Using SQLTalk 12.0.1.10862. If the Execution Plan dialog (which is modeless) is open, then execute a longer running command, such as UNLOAD DATABASE on a database that will take enough time to do this, then while the command is executing, close the Execution Plan window with the X, or System menu-Close, or Alt-F4 (when you can get control of the Execution Plan dialog) , you will get a GCI SEA Session ended abnormally. For a very brief moment, another widow appears, then disappears (so I don't know what it is telling me). Very reproducible...

[Mike Vandine]

Hi Phil,

Perhaps a clarification...

Are you using two SQLTalk sessions? When I use one SQLTalk session, do a 'select * from systables;' then show the execution plan, then go back into the SQLTalk pane and do an unload database command, I can't get to the execution plan window at all. Alt-tab only shows the SQLTalk main screen and the execution plan as one entity and I can't close the execution plan window.

Please let me know.

Best regards,

Mike

[Igor Ivanovic]

Hi Mike,

I can reproduce it also with this steps:
1) connect to db
2) Show Execution plan
3) unload db
now you can't close the plan dialog, but if you
4) Alt-Tab to another app
5) Alt-Tab back to SQLTalk
6) You can close the plan dialog and get the "Session ended abnormaly" error

In my case, if I start SQLTalk again I don't get the error, I get "Program not responding" instead.

[Mike Vandine]

Thanks, Igor.

however, I can't get the session terminated error. I only get the SQLTalk is not responding message. Once the unload is done, the execution plan window is still there and operates as normal.

Best regards,

[phil@informasys.com]

Igor, thank you for the confirmation.
Mike, single SQLTalk instance, single database session.
What was scary is the Session ended abnormally is sometimes an indication of an SB service issue. You know what we've been through since moving to 12.0.
BTW, running everything 32 bit.
Phil