Henry Schubel 5 Light Poster

I have a legacy VB6 application; simple VB6 front end and Access backend database. Works fine on Win 2000, WinXP, Vista, and 32-bit Win7. Bought a new laptop and everything seems to be shipping with 64-bit Windows now. Out of the box, the application worked fine after I manually re-registered a couple of the OCX's for controls. Then Windows went out and did an automatic update of windows, and Microsoft obviously replaced the ADO (Active Data Objects) library, which is where the code is for accessing various databases. The internet is littered with posts about how the newer ADO library kills the functionality of applications that were working just fine previously. And of course, trying to get Microsoft to acknowledge it.... forget it. Does anyone know a fix to allow you to revert back to the original ADO library shipped with 64-bit Win7 ?

Microsoft's marketing lingo... "It Just Works" Ummmmmmmmmm, not it doesn't Microsoft !

jlego commented: but it does work - if you have money to upgrade every time they do! +3