Any brave souls been trying Windows 7? It looks like a really
promising OS. However I've found one nasty problem that manifests
under the last couple of beta builds that isn't a problem in XP or
Vista. It relates to running Access 2003 and 2007 on the same Windows
7 machine.

If Access 2007 is opened and then closed, then the user opens Access
2003 the usual "reinstall" takes place and Access 2003 seems to run as
normal. However there is a problem with the reference to the Microsoft
Access Object Library. Access 2003 now has the "Microsoft Access 12
Object Library" in its list of references instead of its own version
11. This causes all sorts of problems with some databases.

In XP and Vista, the version of Access that is being used, whether
A2003 or A2007, knows which version of the Object Library to use i.e.
Version 11 for A2003 and Version 12 for A2007. Under Windows 7 A2003
gets confused and wants to use Version 12 after A2007 has been used on
the machine.

The fix is to repair the Office 2003 installation in control panel.
A2003 then reverts to using Version 11 of the library, but only until
A2007 is used again, then the problem reappears.

Wayne <cqdigital (AT) volcanomail (DOT) com> wrote:

Sounds like the following problem in Vista.
Errors using multiple versions of Access under Vista
http://allenbrowne.com/bug-17.html

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

On Apr 10, 11:48*pm, "Tony Toews [MVP]" <tto... (AT) telusplanet (DOT) net>
wrote:


Thanks Tony for pointing me to the info on Allen's site. That's
nailed it. It didn't dawn on me that the pesky User Account Control
could be causing the problem. I have UAC turned off in Vista, hence I
wasn't seeing the same problem there. Have turned UAC off in Windows
7 and it's now all good.

Wayne <cqdigital (AT) volcanomail (DOT) com> wrote:

I'm with David. Figure out a means of keeping UAC turned on.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

On Apr 12, 1:30*am, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:


Your point is valid David, but having said that, I have run Vista
since the days it was in beta with UAC turned off and have never had a
problem that UAC would have saved me from. Same for XP which never had
UAC. Maybe I'm wrong here, but with a decent firewall and antivirus,
one has to something a bit silly to get into a situation where UAC
would have saved them. I agree that they've vastly improved UAC in
Windows 7, but in my case to this point it has caused more pain than
it has saved. The subject of my original post is a good example. As
I said, your point is valid and I'm not disagreeing with it, but I
don't think I'll be turning UAC back on in the near future.

On Apr 12, 9:38*am, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:

I think you are drawing a very long bow there David. Does that mean
that none of us cared about security at any level prior to Visa and
UAC? No, we just had to use a bit more care and common sense. And
even now with UAC and without the latter, the user can mistakenly
click "Yes" at a UAC prompt and run malicious software.

On Apr 12, 9:38*am, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:

Don't know how you reached that conclusion David, but you are entitled
to your opinion. There's an interesting discussion here:
http://forums.whirlpool.net.au/forum....cfm?t=1180716 about UAC.
In my opinion the bottom line is that UAC affords the user some
protection by throwing up a prompt to alert them that something's
happening, but if said user then says "OK" to the prompt, even if it
is malware causing the prompt, it's going to run and do its damage.

Having said all that, I've had a rethink and turned UAC back on (at
about half throttle) and have implemented the registry hack posted on
Allen's site to overcome my original problem.

Wayne <cqdigital (AT) volcanomail (DOT) com> wrote:

For competent computer folks who know how to deal with problems such as malware
infestations then I have not too much problem with turning off UAC. Although I
wouldn't recommend it.

That said developers should be running as users and not administrators. When I
first created the Auto FE Updater almost ten years ago I grabbed some code which read
in a registry key from some website somewhere, somewhen. A few years later I was
getting reports of the code puking. Turned out that code's default setting to open
the registry key was read/write when read only was just fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/