Roy,

<< What about you just unprepare the script when F9 is pressed and then
prepare it again? >>

Because it defeats the purpose of preparing the script.  It only needs to be
prepared whenever the script changes.  Besides, it has nothing to do with
this, which is an interface artifact.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< It is that simple. Every time with the script I'm loading. >>

Okay, I finally found it - you have to check the Request Execution Plan
check box on an SQL statement with the same name as the script, i.e. "New"
or something.  Then it occurs.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Okay, I finally found it - you have to check the Request Execution Plan
>check box on an SQL statement with the same name as the script, i.e. "New"
>or something. Then it occurs.

I'll take your word for that, but I assure you I did no such thing. The last time I tested it I simply opened EDBManager, clicked open, loaded the script and pressed F9. I'll report again when 1.07b4 hits the electrons.

Roy Lambert

Roy,

<< I'll take your word for that, but I assure you I did no such thing. The
last time I tested it I simply opened EDBManager, clicked open, loaded the
script and pressed F9. I'll report again when 1.07b4 hits the electrons. >>

You're missing my point - the settings are persisted so the issue would show
itself over and over again as long as the SQL file name matched.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

You never mentioned persistent over a day with the pc turned off as well

Roy Lambert