Cannot unlock a stored report

[Bradnam]

I have created a number of reports, all locked and all working well. I recently changed a couple of these reports and added Connect Parameter options so that a database connection window opens when you run the report. All still OK and working fine...however, I noticed a small problem with one of the reports so tried to edit it - now the unlock icon just flashes between a closed and open padlock and nothing happens i.e. no dialogue box pops up for the password and it stubbonly refuses to let me view the associated code.

I can still edit those reports that do not use any Connect parameters...

Any ideas?

PL/SQL Developer
Version 7.1.5.1398
01.50879 - Unlimited user license
Windows XP Professional 5.1 Build 2600 (Service Pack 3)

 

[Marco Kalter]

Can you open the report definition when you are connected to the database with the connection parameters as defined in the report?

 

[Bradnam]

Marco,

No I can't open the report definition when logged in as the account specified in the connection parameters. This only seems to affect reports where i have clicked the 'locked for other users' radio button. I haven't set a password on any of the reports.

As a test I created a junk report and set the connection parameters username and database - in this case I set the database incorrectly then saved the report. When I run it it obviosly fails as the useername/password is invalid on the database - I then can't open the report the make the necessary amendments.

test 2 - I created a report as account A, while logged in as account A, and added a connection username & database and ticked the 'use this connection' box. This ran OK. I then switched my session to Account B and tried to run the report - this prompted for the password and ran OK but I couldn't edit the report definition. I then switched back to Account A but could still not edit the report definition.

Hope that makes sense.

For the 'broken' reports I needed to amend, I ran Developer in debug mode and extracted the SQl (then dropped and recreated the reports WITHOUT the user locking....

 

[Marco Kalter]

Case 1 might indeed be a problem. Can you send me the report for case 2?

 

[Bradnam]

I just created a new report using a simple select - 'select sysdate from dual;'