Thanks for the reply! Why do you delete foxuser..has it possibly become corrupt?

As an interesting side note. On my dev machine where i had previously been experiencing the problem but only when running one specific report 10-12 times and some days 4-5 times...someone here rewrote the report from scratch..about twenty minute process...and now I dont get the error at all. Does crystal have a utility that you know of for detecting a corrupt report. It seems fairly odd. I was able to open the report in Crystal Reports directly and preview it repeatedly and it never had an error but in our application running the exact same report using the viewer (ocx) it errors out consistently.

Thanks again,

Mike