I cann't understand why there is little complaint about DSO on SQL2005.
Have you updated your codes with AMO completely? Have you forecasted
the competition of other products following up SQL2005 and made enough
preparationg for it?

But we won't, maybe our software will be dead in next competition. But
I am curiouse about others' work currently, since in our product we
have to change quite lots of codes and choose a better and rapid
solution to meet the new platform.

The problem is we can still use DSO to create SQL2005 objects, but it
cann't retrieve them if we operate objects in Management Studio or AMO.

How can you image updating 100 thousand lines of VB codes and replacing
the former DSO? And we made the decision to wrapper DSO with AMO and
product a new DSO interfaces. Which saves time to keep codes on
presentation layer and bussiness layer, but that's a long and difficult
way to approach the new class library structure, and wrapper it to COM
again!