Recent content by Cal Gordy

Installed your 1.2 build 2 and it fixed the notes problem on Win2k Two things would be nice. One is a readme with what changes were made in this build and also an indication of which build is installed in the 'About' box - still just says 1.2 (1.2.2?)

We are seeing this same behavior with notes. We are also running Windows 2000

We have an unlimited license for our organization, so it isn't like this will effect sales. But the full PL/SQL Dev is overly complex for many users. A simple interfact to just run sql reports is very handy so they aren't bogged down with lots of extras. Having an easy, organized way to...

I'm sure this is kind of low investment product for you, but if you ever do some enhancements . . . It would be nice if you could define a default reports directory and then have reports filed under this directorys show up in a heirarchical 'reports' menu like it does in plsql developer.

Thanks for the clarification

In the release notes for the latest release, you mention 'runtime' and 'select-only' version available on request. Would you please provide some more details on what these versions encompass. Thanks

I really think you should implement a full 'editor' for views where you can take full control of the process. Views have enough moving parts with instead of triggers, aliases, comments that a full plsql editor for views would provide a very useful interface. You have one for synonyms of all...

Sorry, but key preserved tables and which columns can be updated are out the window with instead of triggers. Instead of triggers allow us to do what we want, regardless of the normal Oracle rules. We have use of constructs that involve recursions and many to many relationships. Rather than...

Yes - that was our observation. It would be nice if the sql window could either detect the instead of trigger or have some flag that disables the checking and just leaves it up to the database to handle or not in this particular circumstance.

PL/SQL Developer insists on either rowid or for update to allow editing data in a grid. While this makes sense for conventional sql, it is not necessarily a valid requirement for views with Instead of trigger logic that handles the inserts. Unfortunately, there doesn't seem to be an obvious way...

Most excellent - thanks

I am using 6.0.1

Typically with a '/' in username and password field empty. It returns a dialog with ORA-01005: null password given; login denied This same 'syntax' works with sqlplus

Login dialog on 6x does not allow externally identified users to log in. I don't personally use this type of account so didn't notice until some of our users who do pointed it out

I know I keep harping on this subject - but you have sequence editor !!!! I would suggest that views are way more complex and useful to represent in a true editor than sequences.