Word of mouth is that Service Pack 2 for Windows XP breaks the Crystal Reports Designer. Indeed, there's a long list of the things that SP2 breaks. But on Crystal's site, we see this little gem:
|
Status: |
Not a Crystal Problem |
|
Product: |
Crystal Enterprise Professional |
|
Reported Version: |
10.0.0.0 Crystal Enterprise Professional |
|
Applies to: |
All versions |
|
Bit Version: |
32 Bit |
Assuming that they are blanket passing the blame, which kind of seems like they are, the funny thing about this is most developers realize that stuff like this breaks because it wasn't coded according to the best practices at the time. I would venture to guess that if we could peek at the code, the underling problem is BAD CODE. Now, who's fault is it in the end? Of course the majority of the blame lies with Microsoft. Shame on them for breaking such an important application. But, is this “Not a Crystal Problem”? I'd say that it's a BIG Crystal problem. I've never seen the Crystal code under the covers, but I've seen it break enough to know that the underlying code base is probably a mess.
-Brendan
Posted
10-21-2004 9:17 AM
by
Brendan Tompkins