Hi,

If you rename a procedure in EDB Manager and the procedure is being
displayed, than the new name of the procedure will not be updated until
you also perform an Alter procedure (just to click ok, no efective
changes). Also the new name of the procedure will not appear if you
close and start again EDB Manager.


regards,
Lucian

Lucian,

<< If you rename a procedure in EDB Manager and the procedure is being
displayed, than the new name of the procedure will not be updated until you
also perform an Alter procedure (just to click ok, no efective changes).
Also the new name of the procedure will not appear if you close and start
again EDB Manager. >>

Are you executing the RENAME PROCEDURE from an SQL window ?  If so, then
just fit F5 after executing it in order to refresh the explorer treeview.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Are you executing the RENAME PROCEDURE from an SQL window ?

No (sorry for the delay, relocating), please do this:

1. open edb manager
2. open a database (that you know it has at least one procedure)
3. highlight a procedure (the procedure's code should now be visible in
the bottom pane)
4. click on "Rename Procedure" in Tasks pane
5. rename the procedure in the tree, editing the node that has become
editable, hit enter when done
6. (all this time the procedure's code was visible). make note that the
procedure name did *not* change (hit F5 as suggested, still won't
update it)

7. close the database (you would think this would be stronger than an
F5 to refresh)
8. re-open the same database
9. highlight the same procedure
10. note that the procedure name still does not match the tree node text

To really make the node text match the procedure's name from the pane
you will have to go alter procedure and hit ok without making any
changes (the name comes right in the Alter procedure dialog)


I did not test wich name is usable in an application, I don't think it
matters, it has to be fixed.


regards,
Lucian

Lucian,

<< No (sorry for the delay, relocating), please do this: >>

Okay, got it.  A fix for this will be in the next build.  Just a note,
however: this bug is harmless, and is only a descriptive error.

--
Tim Young
Elevate Software
www.elevatesoft.com