Error in a 4GL-report
> From: scheer@stadt-mh.de (Dirch Scheer)
> Subject: Error in a 4GL-report
>
> [...]
> I've written a report called "r_red". Sometimes this report produces an
> error (but it is not reproducable):
>
> Program error at "repvfg.4gl", line number 796.
> SQL statement error number -242.
> Could not open database table (scheer.t_r_red).
> SYSTEM error number -113.
> ISAM error: the file is locked.>
> In line number 796 you can find a "START REPORT r_red". I have never
> created a table "scheer.t_r_red", so I think its a temporary table made
> by INFORMIX at runtime. But why should this temptable be locked by
> another user??? Can anybody explain the mechanism when starting a
> report???
> [...]
Guten tag!
I can't explain these mechanisms adequately, but I use temp tables and
reports all the time with no such problems. You should:
1) upgrade to OnLine 7.1 on a big HP platform. Failing that,
tell us what version you do have so we can comment on
whether it is buggy or not.
2) get Informix support involved. Ask them about version bugs.
3) Say whether you are using SE, OnLine, or what. Are the
permissions correct?
4) Think about incorporating the pid into the report name. This
is a sleazy kludge but it's free and maybe it would fix
your problem.
5) find a way to reproduce the problem. Reduce your variables
by: creating a new database with table with one column
and running a report on that. Do it when no one else is
on the machine.
That's all that comes to mind right now. Good luck with it, these kinds
of problems are hard to solve.
BTW, ich im Deutschland sieben jarhe lieben. Auf Kind.
__________________________________________________________________
| Clem Akins Standard Disclaimers Apply |
|Reynolds Metals Co, Alloys Plant "Climb High, Cave Deep!" |
| Muscle Shoals, Alabama USA cwakins@leia.alloys.rmc.com |
|________________________________________________________________|