.out files result in undeletable tables 1

[SercoSteve]

We have a form which runs a number of queries then prints a couple or reports. The reports use the answer tables generated and other queires contained within the reports.

When the reports print .out files are generated (two for each report, a total of four).

When the print is complete one of the .out files for each print is removed automatically by paradox but one remains.

If we try to run the button again, without closing paradox, paradox complains that one of the tables generated by the previous run is open and cannot be deleted. I think it is because the .out file contains some sort of lock on the table in question.

I cannot delete the .out files without first exiting paradox. Exiting paradox also cures our problem so it is making debugging difficult

All the tables are generated into PRIV.

Any ideas anyone?

Regards

Steve

 

[TonyMcGuire]

The below was submitted by Tom Krieg. The .out files appear to be a red herring of sorts, and appear when you use the dynarray syntax for printing.

> 1) Table locking bug?

If you use a master-child table relationship in a report, and you have a group band on child table fields, the child table remains locked even after the report's been printed. You have to close Paradox to unlock the child table.

I overcome this by extracting to a denormalised, wide report table and use this for printing.