I have some more EDBMgr Suggestions Tim (

Could the system not ask if I want to save a new SQL statement if the statement is blank. If a statement contains SQL which is then deleted leaving nothing the EDBMgr still asks "do you want to save"

Menu Shortcuts "File", "Close" should always close the selected Tabsheet. At present it only closes the selected tabsheet if it is a SQL statement not if it is a table, when [ALT], F, C has no effect.

Creating a new SCRIPT should create a tab with the heading "script1.sql", then "script2.sql" creating a new SQL statement should create a tab with the heading  "New1.sql", then "New2.sql" etc. At present both actions just produce tabs with the heading "New.sql" everytime, making it difficult to spot which is which

Adam

>Could the system not ask if I want to save a new SQL statement if the statement is blank. If a statement contains SQL which is then deleted leaving nothing the EDBMgr still asks "do you want to save"

Reasonable

>Menu Shortcuts "File", "Close" should always close the selected Tabsheet. At present it only closes the selected tabsheet if it is a SQL statement not if it is a table, when [ALT], F, C has no effect.

I always right click and close so I don't care

>Creating a new SCRIPT should create a tab with the heading "script1.sql", then "script2.sql" creating a new SQL statement should create a tab with the heading "New1.sql", then "New2.sql" etc. At present both actions just produce tabs with the heading "New.sql" everytime, making it difficult to spot which is which

+98 thousand!!!!!!!!!!!!!

Roy Lambert

Adam,

<< Could the system not ask if I want to save a new SQL statement if the
statement is blank. If a statement contains SQL which is then deleted
leaving nothing the EDBMgr still asks "do you want to save" >>

I don't know if this should be disabled.  It's one thing if one undo's one's
way back to empty, in which case the modified flag will get reset and you
won't be prompted, but it's another thing to just not prompt for a save
because the statement is now empty.  Emptying the statement could have been
a mistake.

<< Menu Shortcuts "File", "Close" should always close the selected Tabsheet.
At present it only closes the selected tabsheet if it is a SQL statement not
if it is a table, when [ALT], F, C has no effect. >>

The File menu options only apply to SQL files.  Tables and other database
objects all work through the Tasks menu for the object.

<< Creating a new SCRIPT should create a tab with the heading "script1.sql",
then "script2.sql" creating a new SQL statement should create a tab with the
heading  "New1.sql", then "New2.sql" etc. At present both actions just
produce tabs with the heading "New.sql" everytime, making it difficult to
spot which is which >>

I'll see what I can do.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< Could the system not ask if I want to save a new SQL statement if the
>statement is blank. If a statement contains SQL which is then deleted
>leaving nothing the EDBMgr still asks "do you want to save" >>
>
>I don't know if this should be disabled. It's one thing if one undo's one's
>way back to empty, in which case the modified flag will get reset and you
>won't be prompted, but it's another thing to just not prompt for a save
>because the statement is now empty. Emptying the statement could have been
>a mistake.

I think its more a case of why bother saving an empty statement/script. Maybe what it should do, if one exists on disk, is ask if you want to delete it.


Roy Lambert