Beeeeeeeeeeeeves,
I've always hated CR.
That aside, are you sure that you have the designer for the report form
closed? I would make sure that you do not have it open unless absolutely
necessary, and closed all other times. This should at least minimize the
number of times that you see this error. The problem arises from the
designer trying to be too smart in detecting when things affecting the
report cause it to go into an inconsistent state (something I am not
surprized when it comes to CR).
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Beeeeeeeeeeeeves" <Be**************@discussions.microsoft.com> wrote in
message news:0C**********************************@microsof t.com...
I keep getting the above error when working with crystal reports with
vs.net 2003, it happens EVERY time I run the project or save any files
(hence when compiling it) even though I don't use anything other than the
proper editor to modify the file. It is referring to one of the crystal
report files. More worryingly, whenever it does this, it decides to take the
liberty of making the whole screen go completely black for a second or two,
like it does when you change the monitor resolution. This is EXTREMELY
annoying. Anyone know of a resolution?