--0-1492415078-1017336350=:85089
Content-Type: text/plain; charset=us-ascii


Thanks to everyone that gave advice. I am very impressed at the wealth of knowledge concerning this weird error message. 

It turns out that the actual problem was....(drum roll please)...

...the UniqueValue property of one of the queries that creates the report. 


There are three queries that actually make the report. Each query feeding the next. Somehow I inadvertantly turned on the
UniqueValue property of the last query. This was not discovered until I started back-tracking and created a new query from scratch
and compared the two. It turned out that I really did need to use the unque value prop and was able to set it in the first query.
The user determined that the report had been wrong for the past three months.  Figure that. I had mentioned earlier that other
machines could open the report fine. Well that was not entirely true. Only one machine on the network could view it. Not sure why.
The user of this machine downloads LOTS of Access untilies. Could be that.

Anyway, Thanks again. I look forward to being there for you guys.


Lonnie Johnson 
ProDev, Builders of MS Access Databases
http://www.galaxymall.com/software/PRODEV 




---------------------------------
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®