Windows 7 SP1 and changing references (1 Viewer)

[Wedgels]

WARNING! AVOID Windows 7 SP1

Really weird.

I have installed Win 7 SP1 and since doing so whenever I compile an app and accde it it now no longer runs on my target machines. The targets being Windows XP.

I didn't understand it at first but I have done lots of testing and found that old versions of my app that were fine now no longer run at all on older boxes. They act as if one of my references is out of date. If I compile the app and accde it on the target machine - everything is fine. Bare in mind I haven't added or removed any references - just upgraded to SP1.

Now it is not just simply a missing reference but it would appear that SP1 has updated some part of one of the built in Access references and unless recompiled on an older machine - won't run properly when compiles on my Win 7 SP1 box.

Annoying.

Anyone any solutions? - Anyone else seen this or am I just going mad?

 

[Wedgels]

And lo and behold...

http://social.msdn.microsoft.com/Fo...y/thread/186656cb-4e85-440c-be5f-1feea726c467

Someone else with potentially the same problem - although not Access - this would cause my issue.

Microsoft - don't you test things anymore? First the WinPhone 7 update and now this?

 

[Wedgels]

Re: WARNING - AVOID Windows 7 SP1

Yes - it is this problem - but there appears to be some workarounds.

'Just to make this clear: this is not a VB6 only issue.

Any programming language using MDAC COM classes with more specific interfaces than IDispatch will break due to the changed IIDs.'

Other quote:

'I'm having the same problem, installed sp1 on windows 7 and people with no sp1 or people on xp cannot run our software.

Hope that the fix comes quickly, cause I cannot know if all my clients installed sp1 so I cannot install sp1 myself :-('

 

[Wedgels]

Known workarounds:

1. Request a package of KB983246 and install it on your customers' machines. Re-compiled application should work after the package is installed.

2. Re-write your application to use later binding to ADO, or use interfaces with name xxx_deprecated.

3. Keep an old version of ADO typelib (i.e., msado28.tlb) (copy from Windows 7 RTM), then compile your application with the old typelib, instead of the one in your system.

 

[smig]

stupid MS
good find

 

[Wedgels]

stupid MS
good find

Pleasure. Just hope it saves some of you guys some time.

In the end I went down the KB install route. Not ideal for people distributing apps but really - as far as I can see - it is your only sensible option.

 

[gemma-the-husky]

it's an increasing issue though isnt it - especially if you use early binding, and include some of the other "standard" libraries. We now have versions of office from 10 through 14.