S
saintor1
Access 97
This error looks to me as secondary. In fact, it bugs when the
opening report tries to close a form. If I try to open the report
directly, I have a different message, stating that the import
specification name is not present. This because the report is based
on a query that includes a text file that uses that spec.
When opening the linked text files from the tables list, it works.
It is worth noting that the text file is also used in forms (combo)
and there is no issue.
The import specification is present when I look in the table linking
process.
If I delete the link and redo it (with the correct import
specification name), every comes back to normal and the report can be
opened from the form, and the form is closed by the report, as
wished. If I close the MDB and reopen it, the error comes back!
For now, I did a copy of the text file as a table and it works Ok.
However, it is no longer updated by the ERP system.
Any idea? I am mystified. Txs
This error looks to me as secondary. In fact, it bugs when the
opening report tries to close a form. If I try to open the report
directly, I have a different message, stating that the import
specification name is not present. This because the report is based
on a query that includes a text file that uses that spec.
When opening the linked text files from the tables list, it works.
It is worth noting that the text file is also used in forms (combo)
and there is no issue.
The import specification is present when I look in the table linking
process.
If I delete the link and redo it (with the correct import
specification name), every comes back to normal and the report can be
opened from the form, and the form is closed by the report, as
wished. If I close the MDB and reopen it, the error comes back!
For now, I did a copy of the text file as a table and it works Ok.
However, it is no longer updated by the ERP system.
Any idea? I am mystified. Txs