Hi. I'm getting a 'statement not allowed' error on any 'create table as' statement. The same query runs fine in the old version.

This would imply that it is running in "select only" mode. In this case it does not allow DDL statements.

But how do I get 'out' or 'in' to 'select only' mode?

I -think- you are saying my access is 'select only' to the table being updated, but this is not the case. I am actually the owner of the table. If I try the same thing with the old version, logged on as the same user, to the same DB, on the same piece of SQL, it works just fine.

Here are some comparisions of results between versions:

version: 2.0.5.212

'Describe' ==> ORA-00900: invalid SQL statement
'Create table as' ==> works fine
'Drop table' ==> works fine

version: 3.0.0.236

'Describe' ==> ERROR Statment not allowed
'Create table as' ==> ERROR Statment not allowed
'Drop table' ==> ERROR Statment not allowed

These results are for the same piece of SQL, on the same table and DB, with the same access. It's important for our use of this tool to allow 'create table as' and 'drop table' sorts of things, if the Oracle security of the user allows. Otherwise we will be having to drop back to SQL-Plus, truly a scary thought. ;-)

We will make a new beta version available next week, that solves this issue.

We have a fixed version available here:

http://www.allroundautomations.com/queryreporter30b.exe

Apart from the fix for the reported problem, it also has support for unicode in results.

A final version will be available shortly after the release of PL/SQL Developer 7.0.3.

I get the same result with this 30b version. Hmm . . .

My apologies, a mixup on our end. This one will work correct:

http://www.allroundautomations.com/queryreporter30c.exe

Yes, it works fine. Thank you!

I'm an analyst and rely on PL/SQL Developer, but this 'lighter weight' product is used extensively by our users to run very complex queries. Without this product we would really be in a 'world of hurt'.

Thank you for this fine software!