[AccessD] Running Access 2003 and 2010 on same PC

Jack,

 Actually, I should have not said "there is no solution", because Sage found
one with their install scripts.

 As part of that, they figured out a way to isolate Access installs so you
do not get the installation/configuring messages when executing a runtime
that is a different version.  However outside of that, I've never seen
anyone post a solid method for avoiding it other then using a virtual
machine.

 By default, Office from 2003 on "self-repairs" whenever a copy of anything
starts up. This seems to be nothing more then registering the current rev's
components in the registry for use as the default.

 I've never really been able to figure out why it seems worse for Access
more then other Office apps (takes a long time), but it does seem related to
the features you use in each of the products.  But I see the same behavior
in all of them (Word, Excel, etc).

 So that's the part of "by design"; it's the way Microsoft intended this to
work.

 I'd be all ears for a work a round as well, but since this problem has
existed since 2003, I'm not expecting one.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jack drawbridge
Sent: Friday, November 02, 2012 08:48 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Running Access 2003 and 2010 on same PC

Jim,
You may very well be right. I just started with the 2010 stuff yesterday
and I found it extremely frustrating. Also, it seems it doesn't happen to
William. So if William has a solution, I think many of us (at least Steve
and I) would like to see what he has.

That's the issue with the stuff I have found on various forums including
Microsoft Technet and Community-- some say it (Reinstall message and
process) never happens to them; others say Virtual machines is the only
answer;  and some say it's by design.

jack

On Fri, Nov 2, 2012 at 8:34 AM, Jim Dettman <jimdettman at verizon.net> wrote:

> Jack,
>
>  There is no solution because that's the way it works by design.
>
>  It's either put up with it or use Virtual Machines.
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jack and Pat
> Sent: Thursday, November 01, 2012 11:09 PM
> To: AccessD Group Discussion
> Subject: [AccessD] Running Access 2003 and 2010 on same PC
>
> Hopefully someone here has resolved multi versions of Access on the same
> machine. I'm trying to set up 2010 to run along with the trusty 2003 on XP
> sp3. Whenever I move from one version to the other,  I get the Microsoft
> interruption and message that M$oft is reinstalling. It seems a very
> frustrating issue that would have been solved (officially) or a proper
work
> around found and used.
>
> I have searched a lot and have not found a definitive solution. I have
seen
> people who have gone to Virtual PC to separate their different versions of
> Office and Access.
>
> Has anyone solved this? If you're running multiple versions of Acces on
> same
> PC, do you really put up with the reinstalling/reconfig stuff?
>
> Feedback please.........
> Jack
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com