Bug in Studio (2008)

[jec]

Whenever I modify the key field of a table in the ODBC dataconnection table list, everything goes completely screwy. This happens the first time I open and subsequently close the key field chooser dialog. Any clicks on the scroll bar result in the key field chooser dialog popping up several times. This makes it impossible for me setup key fields for all my tables, because I have to save/close and reopen the datasource for every table I want to setup, and I have alot of tables in my schema.

Anyone else experienced this problem?

Joel
Gatekeeper Systems

[dswilson]

What database platform are you connecting to is it file based or RDBMS? If file based is the file external or did you upload it?

Are you using a connection string or a DSN?

Dave

[jec]

I am connecting to an oracle database through ODBC. I'm specifying the datasource by DSN

--joel

[dswilson]

I have just replicated the behaviour. The behaviour is inconsistent. It appears if you click on a row and highlight it by clicking on the far left of the grid and scroll it will work until you click on the field to set the key. It may start acting screwey at this point. If the dialog comes up click cancel and click on another row to select it. Your mousewheel should allow you to scroll to a new row, click it and edit the key. I will log a defect.

Dave

[jec]

Thanks. Please note that once the dialog starts to appear, it continues to appear no matter how I scroll. This includes using the scroll wheel.

--joel

[dswilson]

I was able to stop the repeat sequence by hitting cancel, click on a new row using the gray grid column to select an alternate row (not using the mousewheel) then I was able to scroll. The new row should highlight blue indicating it was selected. It almost appears that focus is not removed from the key field cell and the mousewheel triggers the action which brings the popup.

Dave

[Anonymous]

I can confirm on what both of you said about the problem and the way for
getting rid of it.

Besides, it is slow to retrieve the Oracle objects available under an
existing Oracle schema and populate them in the Show tables grid. In my
case, there are about 270 tables, views and materialized views under my
Oracle native schema, and each time for the database connection, it takes
3-5 minutes for retrieving the available objects and reverse engineering the
existing/foreign Oracle schema. I wonder why the MGE server can not cache
the connection and schema metadata properly, so that the reverse engineering
process doesn't have to be run from scratch each time?

Thanks

Meng

wrote in message news:5688623@discussion.autodesk.com...
I was able to stop the repeat sequence by hitting cancel, click on a new row
using the gray grid column to select an alternate row (not using the
mousewheel) then I was able to scroll. The new row should highlight blue
indicating it was selected. It almost appears that focus is not removed from
the key field cell and the mousewheel triggers the action which brings the
popup.

Dave