When altering a table, view, stored, procedure, or function, the edit
window is in a modal state.  I often find myself wanting to check the
columns of a table while editing a view or stored procedure and either
have to copy the body of the procedure to a separate editor, or make
guesses and later come back.  I can imagine there are very good reasons
for making the editor window modal, but if it's not too much work, I'd
like to see it modeless so I can switch back to the main screen and
view other aspects of the database before closing the edit window.  Or
perhaps have a built-in table reference list of some sort?

One other thing, if I alter any of the above, then immediately hit
Cancel without making changes, only the View will ask if I'm sure I
want to cancel.  Just a slight inconsistency there...


Thanks!

--
David Cornelius
CorneliusConcepts.com
custom designed software

David,

<< When altering a table, view, stored, procedure, or function, the edit
window is in a modal state.  I often find myself wanting to check the
columns of a table while editing a view or stored procedure and either have
to copy the body of the procedure to a separate editor, or make guesses and
later come back.  I can imagine there are very good reasons
for making the editor window modal, but if it's not too much work, I'd like
to see it modeless so I can switch back to the main screen and view other
aspects of the database before closing the edit window.  Or perhaps have a
built-in table reference list of some sort? >>

Actually, I'm looking at moving these dialogs into tabbed windows also.
There's really not reason why I can't simply enforce window uniqueness
vis-a-vis the actual alteration process instead of a modal dialog.

<< One other thing, if I alter any of the above, then immediately hit Cancel
without making changes, only the View will ask if I'm sure I want to cancel.
Just a slight inconsistency there... >>

I'm not seeing this with a procedure or function - both prompt me with an
"are you sure" if I modify the SQL and then hit Cancel.

--
Tim Young
Elevate Software
www.elevatesoft.com

David


Short term workround - open another instance of EDBManager

Roy Lambert [Team Elevate]

> Actually, I'm looking at moving these dialogs into tabbed windows
> also. There's really not reason why I can't simply enforce window
> uniqueness vis-a-vis the actual alteration process instead of a modal
> dialog.

Cool!

> I'm not seeing this with a procedure or function - both prompt me
> with an "are you sure" if I modify the SQL and then hit Cancel.

Right--it's only when you cancel immediately WITHOUT making any changes.


--
David Cornelius
CorneliusConcepts.com
custom designed software

> Short term workround - open another instance of EDBManager

Good idea.  I have difficulties thinking outside of the box at times...

--
David Cornelius
CorneliusConcepts.com
custom designed software

David,

<< Right--it's only when you cancel immediately WITHOUT making any changes.
>>

Duh, my bad.  I've got it now.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

David


No problem. The main reason I know that method is I have EDBManager in the quickstart bar and often double-click rather than single-click

Roy Lambert