When adding an index, or column etc, and the database cannot be updated, it
offers to make a script to do it later. It would be nice to have a checkbox
that just selects to make this script anyway. Then I can see how to make
columns etc and learn from the generated code.

--
Matthew Jones

Matthew,

Why not use the EDBMgr's Explorer > SQL Window (Ctrl+Alt+S) to display the SQL window so when you double click on an item in the tree, like a table or index, you see the SQL that was used to create it?

Or open a new SQL window and drag the table, view, index etc. from the tree to the empty SQL window to see and play with the SQL that was used to create it?

It is not quite the same as Alter Table/Index, but it gives you a lot of info on how the object is created using SQL.

Barry

Matthew

>When adding an index, or column etc, and the database cannot be updated, it
>offers to make a script to do it later. It would be nice to have a checkbox
>that just selects to make this script anyway. Then I can see how to make
>columns etc and learn from the generated code.


It might be, but then I would be denied the pleasure of suggesting you look in Explorer | SQL History

Well at least for code that's actually worked.  For the stuff that doesn't work you have the option you describe.


Roy Lambert

Barry wrote:

> Why not use the EDBMgr's Explorer > SQL Window (Ctrl+Alt+S) to
> display the SQL window so when you double click on an item in the
> tree, like a table or index, you see the SQL that was used to create
> it?

Ahah, that's a particularly handy feature. Can you tell I'm new to
this? 8-)

--

Matthew Jones

Roy Lambert wrote:

> It might be, but then I would be denied the pleasure of suggesting
> you look in Explorer | SQL History

More delicious goodies! I'm glad I asked...

--

Matthew Jones