Good day!
I have a report that - more often than not - works just fine. Occasionally, it chooses to return #Errors in all controls. Upon going back and trying again, it works as it should. I have been unable to recreate this error.
The report asks for the user to choose a date. I am wondering if the report is behaving badly if there is some incomplete data entry for the user-selected date? For example, the manager tries to print yesterday's report and her data entry people are finished entering yesterday's data. I would think the report would give whatever is already completed, no? This is just a theory... as I said, I've been unable to recreate the error and it does eventually provide the manager with the complete report.
Ideas?
Thanks,
Michele

IS your date comaprison for your report between the # symbols? If not, maybe sometimes it is recognizing hte date and sometimes not? Or as you said, there could be one field somewhere without info in it at the time of the run and it is causing the #Error (dividing by 0 would cause this). I'm not sure otherwise. Sounds to me like a definate data issue if it works usually. Everytime I get someone here that has this issue on a report that was working, I can go back and find where they deleted infor from all fields of a record instead of deleting the record or something similiar.

Good luck!!

J

Mr. VanKirk,

Thank you for your reply.

I checked the tables... everything seems to be in order. I guess that's just it - maybe they weren't done when the manager tried to print. To answer your question, no, the date isn't between #'s - it's from a query whose criteria is [Enter Date]. I will just leave it alone. It's not really broken... so why fix it? Since it usually works, I'll just remind her to wait until she knows they're done (which she knows because they email her an excel version of what they've just completed)(she just prefers the frilly report from Access).

Thanks again for your help!
Michele