err "The object you referenced isn't an OLE object"

[Guest]

I recently added some design changes to my access database and started
getting the following error "The object you referenced in the visual basic
procedure as an OLE object isn't an OLE object." Anyone with a cause and/or
solution for this problem?

 

[solex]

Dear Acess programmer,
where is the error occuring?

 

[Guest]

Dear Solex,
The error message comes up when any report is opened. Also I need to tell
you that this error is intermittent. I've experenced both the report going
ahead and opening okay after closing the error dialog box and the report
opening with no data. There is not any consistency to this. I also can
compact and repair the db and the problem will abade for a session or two and
then come back. I hope this further explaination helps.

 

[solex]

I'm not sure I can be of help here, as it is difficult to debug an
intermitten problem. How complicated is your report? Have you tried
recreating your report as a different report?

Dan

 

[Guest]

Thanks anyway. I'm an experienced Access programmer and there is nothing
wrong with my report. I just needed help as to what this particular error was
trying telling me since I do not have an OLE object in my report. Also since
the error is intermittent I figure it has something to do with timing. I
would like to find out what triggers this error message to help me debug my
design. I was hopeing to find someone who has experienced the error message.
Don