I'm not convinced that the Crystal Reports "Exception" is a real deal in my case because of two conflicting scenarios
- I restored from Version Control, pulled out all but two of the existing fields in the xsd element I wanted to replace. I modified the query to pull from a different table. I added one field of the two I need into the element, and when I added the 2nd one, I got the exception. I could not make the exception go away by backing off the work I'd done.
- I restored from Version Control, pulled out all but two of the existing fields in the xsd element I wanted to replace, and got the exeption right then.
Either I get the exception uniformly or something else is in play.
I always tell young developers "If it didn't do this earlier today, and it doesn't make sense, reboot". So I tried. When the PC came back up, it came back up strange and had to be hard booted again, so I'm wondering if I've had a resource problem all along. We'll see in the morning.
posted @ Tuesday, November 07, 2006 9:23 PM