I have two deployments of an application and cannot run my reports in either. In one, the reports appear in the "Open" window when running Reporter in development mode. However, when I select a report, I get "File does not exist". Application Manager shows the reports but gives "The report or query is locked by another user" when I try to open a report.

In the other deployment, I cannot find the reports at all even though all other application components are present and working and I did not delete any reports.

SCAN_REP shows no reports. I went back and "undeployed" everything and Application Manager shows no checked out reports. Rebuilding the system indices did not help.

Any ideas?

Hi Bob

Sorry this seems a bit late but I've been on OI free holidays. Email free as well.

The reporter reports seem to live in a table called SYSREPOSREPORTS. You could try a dirty fix along the lines of copying the sysreposreports dos file from your system to the clients (suggest backing up the client's copy FIRST). In my system the dos files are REV30057.* (you need the *.ov and the *.lk) in the OINSIGHT directory. You can find this out for your system using system editor to 1. open a record in sysreposreports, 2. close it, 3. open the sysreposreports record in systables, the rev file name is in that systables record, line 5 the bit starting with "REV". Very very grotty.

The way my client was making things disappear was to save them in places other than the "repository". This may be good if you want to stop people from modifying standard reports, but not so good if they forget where they saved the thing. Reports are saved with names like *.rpt in what ever path you (or your clients) may have chosen.

Since I know nothing about deploying anything using the standard systems, I would probably check the report out then check it back in the client's system or do a file save as from reporter to a temp report name in a temp directory then get the .rpt file, take that to the client site, stick it in a suitable directory then use reporter to open it, then maybe do a file save as to get it in to the repository.

Mostly I avoid using reporter because I can't "predict" the reporter output from known input reliably, especially when the tables get really big. One of my clients insists on using it anyway.

Scott, LMS

What OI version? This sounds like an older REPORTER bug.

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...