Hi

I have a report that is invoked from a dialogue.
In the dialogue you select the actual name of an output .dbf to print.
All such output files have the same format and field names
The report, of course, has no DE, and all the controls have merely the field names from the output files as source.
I have two other very similar reports but, when I go to edit this one, I get a "Locate Database" error dialogue that says:

"Error instantiating cursor object. Cannot find {path}\A3tp2_1a.dbf" - locate, ignore, etc.

Now this file happens to be one of the user-generated output tables that has been used by the report in the past. This error message has never come up before, and doesn't happen with the other similar reports. So it seems that somehow this report has managed to get a cursor name "embedded" in it, almost as in the DE.

I'm allowed to "ignore" and go on to edit the report.

Any ideas how this came about, or how I can get rid of it?

Also, note that I get the "Locate Database" error dialogue, like you get when VFP can't get the back-link of the DBC for a database table.

Could this be a "throw-back" to the old FPD days when tables were called databases, and the wording slipped in unnoticed?

Or, what gives?

Perplexed

Terry