ADO issues with Windows 7 SP1

This is probably more of an announcement than a question.  I develop / maintain about 12 Access applications.  A couple of months ago I got a new system with Windows 7.  It’s been working great, but since I installed (i.e. allowed Windows Update to install) Service Pack 1 I have experienced significant issues with any application I have compiled when it is run on any system not using Win 7 SP1.  I traced the issues to ADO calls in my code (Recordset and Connection objects particularly).  My reading of the forums indicates this is a widespread problem affecting any development environment that uses ADO libraries.  Apparently Win 7 SP 1 installs a whole new set of ADO libraries, and though all the file names are the same, the file sizes are different and apparently the identity and function is altered as well, since my apps now throw various 430 and 91 errors.  

Couldn’t they have just called this ADO 3.0 and left 2.7, 2.6 etc. as they were?  This ADO update breaks backward compatibility in a big way, and of course was done with no notice I’m aware of.  I’d like to call Microsoft stupid, but this is actually very clever.  They’ve made a major structural change that no doubt suits their purposes, but did it in a way that ensures that the developers and sys admins will catch all the flak when the inevitable problems occur.  These links offer further explanation, but nothing I call a solution.  Anything from EE would be appreciated.

http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/3a4ce946-effa-4f77-98a6-34f11c6b5a13

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/04874992-e2e6-4ec1-98c6-c937fafbc958
Smart_SystemsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
This is a known issue and Microsoft is aware ... via the MVP channel, wherein it was reported 3-4 weeks ago by 2-3 MVP's.

mx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Smart_SystemsAuthor Commented:
Thank you mx.  Do you have any idea what kind of solution might be fortcoming - rollback, patch, ? - or when it might be available?  I understand that uninstalling SP 1 solves the problem, but I wouldn't bother with that if I thought a better solution was on the way.
0
Rey Obrero (Capricorn1)Commented:
to date, to solve the problem is  to uninstall sp1 as discussed by DAHAN C in the first link that you posted.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Gustav BrockCIOCommented:
Read more here:

An ADO application that is re-compiled on a Windows 7 Service Pack 1-based computer does not run on down-level operating systems
http://support.microsoft.com/kb/2517589

/gustav
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I assume you could glean this from the links provided, but for the benefit of other who might run across this:

From what I've seen, the "fix" is to either (a) uninstall the Service Pack or (b) use Late Binding.
0
Smart_SystemsAuthor Commented:
Thanks to all for your responses.

There are some "fixes" discussed on MSDN; the ones some of you mention and some other arcane nonsense about altering dll identifiers and re-registering them, etc.  The consensus is that most of these fixes are unworkable, since they involve dealing with every single client machine or rooting through apps and changing every line of code that calls ADO.  The simplest one (but still evidence of what a bogus move this was by MS) is to uninstall SP1, which is probably what I will do if a fix is not issued by MS soon.

I'd like to leave this question open for another day or two just to see what else turns up.  My main purpose in posting was to provide some information that would appear in response to a search for the words in my question title.  When I first searched EE there was only one return that even came close, and it was focused on problems with 64 bit machines.  This problem is proving to be far more widespread.
0
donhannamCommented:
Thanks for the post - I spent hours trying to work out what this was about.

Agree only workable solution is to uninstall Service pack 1.

The error message I had most was "Class does not support Automation or does not support expected interface"

Out of interest I did download and install the hotfix from Microsoft on one of my clients PC's and it did allow an ade I compiled in SP1 to run on their PC. Not practical for me to roll this out to all client Pc's so hoping Microsoft comes up with a solution.
0
Smart_SystemsAuthor Commented:
It's been a few days now and not much new has emerged.  MS is talking about a fix, but acknowledging that it could be a while, since there are now developers and users on both sides of the Win 7 SP1 line and it's going to be hard to find a fix that works for everybody.

I did uninstall SP1 and that put things back to "normal" immediately.  A few people have reported problems with the uninstall, but for the most part it seems to be the solution of choice at the moment.  This link to MSDN has proven to be the best way to stay current on the issue.

http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/3a4ce946-effa-4f77-98a6-34f11c6b5a13

Thanks to all the Experts.  You're always much appreciated.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.