WARNING: Do not use Vista for multiple versions of Access!

[Allen Browne]

If you develop for others, you probably have multiple versions of Access
installed so you can edit and create MDEs for clients in different versions.
This works fine under Windows XP, even with Access 2007 installed.

It does *not* work under Windows Vista Ultimate. After running Access 2007,
when you open an earlier version of Access, no code works, because the
references are fouled up. And Access 97 does not work at all.

Access should adapt the Access library according to the version of Access
you are using. Under Vista, this doesn't happen, so Access 2003, 2002, or
2000 attempt to use the Microsoft Access 12.0 library. Naturally enough,
that fails. You cannot just uncheck the bad library and choose the correct
one, since it is a required library.

You can "repair" your Access install, which works until you run Access 2007
again. Office already does a lengthy reinstallation whenever you switch
versions, so this is not a practical solution.

I've experienced this on Vista Ultimate, and the same was true of the user
who raised this in microsoft.publi c.access.formsc oding. In cannot say if it
applies to other versions of Vista, but since the problem appears be be the
interaction between Office and the Vista registry, I don't see a reason why
it would be limited to Ultimate.

If there does turn out to be a simple solution for this, hopefully we will
hear soon. In the mean time, stay with Win XP if you use multiple versions
of Access.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Rick Brandt]

Allen Browne wrote:

If you develop for others, you probably have multiple versions of
Access installed so you can edit and create MDEs for clients in
different versions. This works fine under Windows XP, even with
Access 2007 installed.
It does *not* work under Windows Vista Ultimate. After running Access
2007, when you open an earlier version of Access, no code works,
because the references are fouled up. And Access 97 does not work at
all.
Access should adapt the Access library according to the version of
Access you are using. Under Vista, this doesn't happen, so Access
2003, 2002, or 2000 attempt to use the Microsoft Access 12.0 library.
Naturally enough, that fails. You cannot just uncheck the bad library
and choose the correct one, since it is a required library.

You can "repair" your Access install, which works until you run
Access 2007 again. Office already does a lengthy reinstallation
whenever you switch versions, so this is not a practical solution.

I've experienced this on Vista Ultimate, and the same was true of the
user who raised this in microsoft.publi c.access.formsc oding. In
cannot say if it applies to other versions of Vista, but since the
problem appears be be the interaction between Office and the Vista
registry, I don't see a reason why it would be limited to Ultimate.

If there does turn out to be a simple solution for this, hopefully we
will hear soon. In the mean time, stay with Win XP if you use
multiple versions of Access.

Thanks for the heads-up Allen. Just to clarify though...are you saying that
even if Access 97 is the only version installed it will not work under Vista or
just that it cannot be repaired after running Access 2007 like the others can?

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Allen Browne]

You can get Access 97 working again by installing it again.

But unless you reinstall it again each time you need to use it, it fails to
start with the dialog:
Microsoft Access can't be started.
Microsoft Access was unable to initialize the Windows Registry
Rerun Microsoft Access or Microsoft Office Setup to reinstall Microsoft
Access.

At this stage, I think my best option is to blow away the Vista install and
start over with WinXP. (I don't think I want to set up virtual machines to
handle the previous versions.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Rick Brandt" <ri*********@ho tmail.comwrote in message
news:b8******** *********@newss vr11.news.prodi gy.net...

Allen Browne wrote:

>If you develop for others, you probably have multiple versions of
Access installed so you can edit and create MDEs for clients in
different versions. This works fine under Windows XP, even with
Access 2007 installed.
It does *not* work under Windows Vista Ultimate. After running Access
2007, when you open an earlier version of Access, no code works,
because the references are fouled up. And Access 97 does not work at
all.
Access should adapt the Access library according to the version of
Access you are using. Under Vista, this doesn't happen, so Access
2003, 2002, or 2000 attempt to use the Microsoft Access 12.0 library.
Naturally enough, that fails. You cannot just uncheck the bad library
and choose the correct one, since it is a required library.

You can "repair" your Access install, which works until you run
Access 2007 again. Office already does a lengthy reinstallation
whenever you switch versions, so this is not a practical solution.

I've experienced this on Vista Ultimate, and the same was true of the
user who raised this in microsoft.publi c.access.formsc oding. In
cannot say if it applies to other versions of Vista, but since the
problem appears be be the interaction between Office and the Vista
registry, I don't see a reason why it would be limited to Ultimate.

If there does turn out to be a simple solution for this, hopefully we
will hear soon. In the mean time, stay with Win XP if you use
multiple versions of Access.

Thanks for the heads-up Allen. Just to clarify though...are you saying
that even if Access 97 is the only version installed it will not work
under Vista or just that it cannot be repaired after running Access 2007
like the others can?

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Darryl Kerkeslager]

On a scale of 1-10, this sounds like a really bad problem.

--
Darryl Kerkeslager
"Allen Browne" <Al*********@Se eSig.Invalidwro te

It does *not* work under Windows Vista Ultimate. After running Access
2007, when you open an earlier version of Access, no code works, because
the references are fouled up. And Access 97 does not work at all.

[cut]

You can "repair" your Access install, which works until you run Access
2007 again. Office already does a lengthy reinstallation whenever you
switch versions, so this is not a practical solution.

[cut]

If there does turn out to be a simple solution for this, hopefully we will
hear soon. In the mean time, stay with Win XP if you use multiple versions
of Access.

[DMeister]

Does anyone have experience with an independent runtime install (e.g.,
Sagekey) of 97 or 2000 and Access 2007?
"Darryl Kerkeslager" <ke*********@co mcast.netwrote in message
news:ov******** *************** *******@comcast .com...

On a scale of 1-10, this sounds like a really bad problem.

--
Darryl Kerkeslager
"Allen Browne" <Al*********@Se eSig.Invalidwro te

It does *not* work under Windows Vista Ultimate. After running Access
2007, when you open an earlier version of Access, no code works, because
the references are fouled up. And Access 97 does not work at all.

[cut]

You can "repair" your Access install, which works until you run Access
2007 again. Office already does a lengthy reinstallation whenever you
switch versions, so this is not a practical solution.

[cut]

If there does turn out to be a simple solution for this, hopefully we

will

hear soon. In the mean time, stay with Win XP if you use multiple

versions

of Access.

[John Vinson]

On Wed, 27 Dec 2006 23:02:36 +0800, "Allen Browne"
<Al*********@Se eSig.Invalidwro te:

>If you develop for others, you probably have multiple versions of Access
installed so you can edit and create MDEs for clients in different versions.
This works fine under Windows XP, even with Access 2007 installed.

It does *not* work under Windows Vista Ultimate.

YOW.

Thanks, Allen. I've never been an "early adopter" and this warning
reinforces that prejudice!

John W. Vinson[MVP]

[Lynn Trapp]

On a scale of 1-10, this sounds like a really bad problem.

>

On a scale of 1 - 10, I would say this is about a 15. <g>

--

Lynn Trapp
Microsoft MVP (Access)
www.ltcomputerdesigns.com

[Steve Schapel]

DMeister,

AFAIK, Sagekey do not yet have a runtime installation script for Access
2007.

--
Steve Schapel, Microsoft Access MVP

DMeister wrote:

Does anyone have experience with an independent runtime install (e.g.,
Sagekey) of 97 or 2000 and Access 2007?

[David W. Fenton]

"Allen Browne" <Al*********@Se eSig.Invalidwro te in
news:45******** *************** @per-qv1-newsreader-01.iinet.net.au :

I've experienced this on Vista Ultimate, and the same was true of
the user who raised this in microsoft.publi c.access.formsc oding.
In cannot say if it applies to other versions of Vista, but since
the problem appears be be the interaction between Office and the
Vista registry, I don't see a reason why it would be limited to
Ultimate.

Is the registry change being made in HKLM or on HKCU? If the latter,
then you could run different versions on different user logons.

But I'm not otpimistic about that.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"Allen Browne" <Al*********@Se eSig.Invalidwro te in
news:45******** *************** @per-qv1-newsreader-01.iinet.net.au :

You can get Access 97 working again by installing it again.

But unless you reinstall it again each time you need to use it, it
fails to start with the dialog:
Microsoft Access can't be started.
Microsoft Access was unable to initialize the Windows Registry
Rerun Microsoft Access or Microsoft Office Setup to reinstall
Microsoft
Access.

Doesn't A97 have to run under an administrative logon, or have the
registry permissions tweaked to allow it to write to them? Is it not
the case that Vista locks down the registry even more than Win2K and
WinXP, and that this will cause issues with A97 if all you do is
install it with default settings?

Would it be possible to protect certain registry keys from change so
that A2K7 couldn't do this?

Or could you export the correct registry keys, then re-import them
after A2K7 changes them? You could then use a batch file to launch
other versions of Access that would repair the registry before the
app runs.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/