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.