[AccessD] Using ADO and Windows 7 SP1? Be careful!

Hi Bill et al

There is a lengthy discussion on this here:

http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/3a4ce946-effa-4f77-98a6-34f11c6b5a13

However, it doesn't add much as the essentials seem to be updated in the KB article posted below by Doug.

/gustav


>>> bill_patten at embarqmail.com 31-03-2011 20:27 >>>
I am having similar problems with 2 clients. I just moved an ADP Access 2003 
from my development machine (Win7 64 SP1 ) to an XP machine, decompiled it, 
set the reference to activex 2.6 from 2.7 recompiled,  repair and compacted 
and shipped it. It now works on one machine that it did not work on. They 
will let me know later about the other machines as people start to use the 
application.

What is really strange it always worked on some of their machines and we 
were not able to find any differences in versions or references.

The second client is running it on Windows Server 2003. I have access to it 
using LogMeIn so will experiment tonight to see if changing the active x 
reference, or decompile compile on an XP machine or both fixes it.

Many other people seem to be removing SP 1 from their development machines, 
but I'd rather not go backwards, course I've been known to cut off my nose 
to spite my face.
If I learn anything new tonight I'll let you all know.

Bill

--------------------------------------------------
From: "Doug Steele" <dbdoug at gmail.com>
Sent: Thursday, March 31, 2011 11:09 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Using ADO and Windows 7 SP1? Be careful!

I believe so, from reading the discussions.  I was able fix the
problem by removing the ADO reference on the client machine, compiling
(got errors on missing reference) then reinstating the reference and
compiling once more.  I'm not sure if the first compile step does
anything, but it doesn't do any harm.

Doug

On Thu, Mar 31, 2011 at 10:47 AM, John Bartow <john at winhaven.net> wrote:
> Hi Doug,
> Just for clarification purposes, if the compiled access database running 
> ADO
> is compiled on anything older than W7SP1 does it still work correctly on
> W7SP1?
>
> John B.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele
> Sent: Wednesday, March 30, 2011 9:59 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Using ADO and Windows 7 SP1? Be careful!
>
> I had a call from a client this morning.  Some code that I had written 
> using
> ADO to write records to a back end, code which has been working for 2 or 3
> years, was crashing with a message indicating that ADO wasn't working.
> Unfortunately, it was a bit of a panic situation and I didn't get a screen
> dump of the message.  I putzed around with the references and 
> re-compiling,
> and got it to work.  Turns out that this is probably an example of a known
> problem:
>
> http://support.microsoft.com/kb/2517589 
>
> There is also a discussion (well, a bunch of bitching) about this in the
> LinkedIn Access Developers group.  If I understand it correctly, an Access
> database using ADO which is compiled on a computer running Windows 7 SP1
> will NOT run properly on any other version of Windows.
> I`m running Win7 SP1 and my client is Win7, so I guess this was the 
> problem.
>
> I wonder if I can send an invoice for my debugging time to Microsoft...
>
> Doug