Doug Murphy
dw-murphy at cox.net
Fri Nov 2 12:30:26 CDT 2012
My original response on this thread may have been too brief. My approach to versioning is to use Virtual Machines. I use VM Ware Workstation which I depend on daily. Have several different servers set up plus all versions of Windows back to 98 and office to 97. I use most of this for software testing but do development on some also depending on client requirements. I started with VM Ware on my last computer a 7 year old Pentium with 3 G of memory. Worked fine and would run as host with 2 VMs running. New computer is I7 with 12 G. I have not used Virtual Box but several folks have reported good service from it. It is free. I previously had several machines with various versions of office etc for test and development. Virtual machines have eliminated this requirement. Also great for client problem testing as I can duplicate their OS and Office versions. Sagekey gets around the versioning issue for their runtime installations by using a little startup exe that sets the registry for the version they are starting and then resetting to what was there before their application started. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jack drawbridge Sent: Friday, November 02, 2012 7:25 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Running Access 2003 and 2010 on same PC Thanks for getting back William. We were hoping you had the "fix". I wish I knew more about the registry or even file associations, since it seems that may be where and why the issue arises. I have a 1 gb older machine running XP, so perhaps some new hardware either for A) a more meaningful Virtual machine to separate the Access versions, or B) as Mark suggested, to physically separate them. (Dell, HP and Lenovo must love this approach) I can just see some people having to put 2003, 2007, 2010 and 2013 on different physical machines. If anyone has more info -- We're all ears. Thanks. PS I think I'll go back and read John C's iStory to put this all into perspective. On Fri, Nov 2, 2012 at 10:02 AM, William Benson (VBACreations.Com) < vbacreations at gmail.com> wrote: > Sorry, I was wrong, I do get those messages as well. I am not sure why > I thought I got past it.... maybe because I just watch MS do its thing > and it requires no effort from me so I ignore what's going on and wait > out the 20 or so seconds it makes me wait. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jack > drawbridge > Sent: Friday, November 02, 2012 8: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 > > -- > 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