Stuart McLachlan
stuart at lexacorp.com.pg
Mon Aug 22 20:37:24 CDT 2011
It was nowhere in the chain of security fixed and bug fixes. It was the implementation of one of those "few extra bits of functionality" that broke everyone's ADO. It's starting to look like one of those things that is difficult if not impossible to fix without completely breaking backward compatibility. Personally, I'm not really bothered about it. I'm so glad that I stuck with DAO/ODBC and didn't get sucked into the ADO path. :-) -- Stuart On 22 Aug 2011 at 21:10, William Benson (VBACreations. wrote: > Hey Darryl, > > Exceptionally clear, well written answer, thank you very much! > > Here is what was written recently about SP1 .. and by the way I have > seen this in more than one place: > > If you haven't installed anything off Windows Update in a while, > first, shame on you! It's important to keep yourself updated! Also, > this release is essentially a big fat roundup of all the security > fixes and bugfixes since Windows 7 was released, combined with a few > extra bits of functionality. If you have Windows Update set to > automatic, the service pack will not make you more secure. > > > > So my question is, at WHAT POINT in the long chain of security fixes > and bug fixes did Win 7 go from being > Win-7-with-security-fixes-and-bug-fixes ... to lethal app killer? > > Seems strange not to have run into this problem along the way some > place... either that or else SP1 is not as described above. > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >