error message when trying to run a report

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have my common used reports on a front end form. I try to run one that
prevoiusly worked and I get the error - "Item not found in this collection"
 
Make a backup copy of the MDB file, and then try a compact/repair:
Tools | Database Utilities | Compact repair.

If that doesn't solve it, we will need some more information:

a) Are you able to open this report in design view?

b) What version of Access is this?

c) Do you use a print attached to your computer, or a network printer?

d) Presumably other reports work fine. What is the name of the problem
report?

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

message
news:D[email protected]...
 
Make a backup copy of the MDB file, and then try a compact/repair:
Tools | Database Utilities | Compact repair.

If that doesn't solve it, we will need some more information:
Click to expand...
I did a compact repair and that did not work.
a) Are you able to open this report in design view? Yes, I can open in design view

b) What version of Access is this? Access 2002

c) Do you use a print attached to your computer, or a network printer? Network printer

d) Presumably other reports work fine. What is the name of the problem
report?
Click to expand...
All other reports work. It is a selected EE report, you choose a date
range and an employee (from a drop down list) and select generate report.
 
From your last comment, I take it that you get this error when you open the
report from a form.

The error indicates that something is referring to a name Access can't find.
The problem could be in the report, or it could be in the code that opens
the report.

Do you get the error if you go to the Database window, click the Reports
tab, select the report, and click Preview?
- Yes: the problem is in the report.
- No: the problem is in the code that opens the report.

Use similar techniques to continue to pin down where the problem lies until
you find the culprit.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

message
 
Back
Top