>Well, some perhaps, but the reporting issues are serious, IMHO.

I haven't covered all the reporting bugs in my blog series yet. But there is only 1 reported bug that is new in SP2 core involving reporting. And I will be offering a ReportListener workaround for it. There are 2 behavior changes in SP2, but I would not consider them bugs.

I think the bug should be fixed, but it's not going to stop me from upgrading. There are new features and fixes in SP2 that are more signicant to me.


> And it does not make me have that warm and fuzzy feeling when M$ seems to be ignoring the problems.

Microsoft has been addressing reported issues. (The fixed help file is on it's way). I think they would address other issues too. I also think there are undisovered bugs in SP2, but we aren't finding them because with all the hype, many people are not even installing SP2 to find them.


> Why move to a potentially unstable platform when I have a stable one. I'm not sure what in SP2 is really required for my work. I'm not interested in the DBI controls, since ActiveX sometimes opens its own can of worms.

The DBI controls are part of Sedna, not SP2. I know it requires SP2 to install, but you should have SP2 installed on your machine anyway. This way you can report any issues you find while testing your app using SP2. You can have SP1 and SP2 installed at the same time. If SP2 is causing so many problems for you, please report them. Otherwise when/if an SP3 comes out, your issues will be fixed also.

If you never report your SP2 issues, because you are not even going to install it...you wait for SP3...then your unreported issues are still in SP3...

Don't think you are going to get an SP4.

I know it stinks and we "should not have to do it". But if you want a better product, you are going to HAVE to test SP2 and get the issues reported.

I'm not saying to shove SP2 at your clients. Get SP1 and SP2 installed (see Rick Schummer's white paper) and at least give your apps a run through in SP2 to see if they are really broken.