[AccessD] FW: W7 SP1 breaking ADO

Pretty much at this stage for anyone using VBA, that is it and that is what I did.  Of course for some folks that is not an option.  Two examples I can think of are 1: folks on corporate networks who get the OS updates pushed out to them, and folks who recently purchased W7 that has SP1 already built in.

I got lucky, the rollback to W7 Release version worked and all was good again.

Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Wednesday, 23 November 2011 2:39 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] FW: W7 SP1 breaking ADO

It seems that the only fix is to remove SP1.
A.

On Tue, Nov 22, 2011 at 10:33 AM, Edward Zuris <edzedz at comcast.net> wrote:

>
>  There are also problems with DAO and large query statements.
>
>  Along with the AppHangB1 error have been getting AppCrash errors  for 
> VBA programming that works fine on W2K and XP OS systems.
> I am not yet sure which approach we will take, we are still trying to 
> figure this out.
>
> We might try to stay with Win XP SP3 for our Development box for the 
> short term or we may make the changes for Late Binding.
>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com