[AccessD] W7 SP1 breaking ADO

Brad,

I can't answer your question about has it been fixed yet but can tell you my 
solution.

I continue to develop in my win 7 64 bit machine, then when I am ready to 
ship I move the ADP in most cases (but it also works with an MDB) to an XP 
VM or I also have an XP test machine, then decompile/ re-compile and ship 
from that machine to my clients.

Bill

--------------------------------------------------
From: "Brad Marks" <BradM at blackforestltd.com>
Sent: Monday, November 21, 2011 10:01 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: [AccessD] W7 SP1 breaking ADO

All,

Several weeks ago, there were a number of posts here in AccessD
regarding a problem with W7 SP1 breaking ADO.  I read these posts but
did not quite understand the problem.  Because this issue did not affect
the work that I was doing, I did not dig very deeply into this issue.

Now things have changed, and I need to better understand this issue.

We might start to use a Windows 7 box for Access 2007 development
(possibly Access 2010).  The Access applications will be deployed to
some users who have Win XP SP3 and some running under Windows Server
2003 R2 Enterprise Edition SP2 (via Terminal Services).

I have some dumb questions.

Is the crux of the problem caused by using 64-bit for Development and
32-bit for Deployment?

Is the problem limited to W7 SP1?  Can you run W7 without SP1?  Is SP2
available?  Does it fix the problem?

It looks like we can either stay with Access 2007 or move to Access
2010.  Does this make a difference with regards to this problem?

Thanks,
Brad


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com