Access startup delays

[Kowalski]

Hi
Similar problems has been discussed in a number of other forum threads across the web, so I hate to bring it up once again, but I would like to know if anyone has got a real, working solution because nothing else works (for me anyway).

Problem case:
I have Access 2002 (or 2003) installed. Now I install Access 2010 or just an app created in Access 2010 (with the 2010 runtime). Every time I switch between runtimes and open up the other access version I get the message "Please wait while Windows Configures Microsoft Office Single Image 2010"
I'm running on a 32 bit machine - Windows XP.

I've tried a lot of suggested solutions from formatting PC, uninstallting and reinstalling Access, changing the registry, running SubInACL.
I also do not have a registry cleaner installed which seems to cause some of the problems on other people's PC's.

 

[gemma-the-husky]

I thought I posted a reply.

I looked at a paid-for product a while ago that dealkt with this.

might have been this, but it isn't cheap!

http://www.fmsinc.com/microsoftaccess/VersionLauncher.asp

 

[Kowalski]

Thanks for the reply. I downloaded the trial version but it's a no-go. It does not solve the problem.
It also supports upto Access 2007, and not 2010.

 

[Galaxiom]

Unless I misunderstand the question enitrely, that is what always happens when you have more than one version of Access (including runtime versions) installed on one computer.

The only solution is to install one of the versions into a virtual machine.

 

[Kowalski]

Hi
Thanks, but the virtual machine option is not really an option, as the problem actually happens on the client's PC when we deploy our Access 2010 apps. We can expect every client to install a Virtual Machine for the apps.

 

[Galaxiom]

If the client's machine already has a different version of Access on it then AFAIK there is no solution.

It is certainly true for 2007 with earlier versions but I don't have any experience with 2010. Maybe Microsoft did something for it.

 

[gemma-the-husky]

Hi
Thanks, but the virtual machine option is not really an option, as the problem actually happens on the client's PC when we deploy our Access 2010 apps. We can expect every client to install a Virtual Machine for the apps.

maybe it's an issue you should address

could you not produce a version for use with A2003 and a version for use with A2007/A2010. Thats what I do.

 

[Kowalski]

In this case it's not an option. The app was in an older version (97) but they requested and paid for the upgrade to 2010, so giving them a 2003 version will be about the same as what they had previously.
Thanks for the replies.


[note by G-T-H. I inadvertently edited this post, when intending to post a reply. The post has not been edited]

 

[gemma-the-husky]

In this case it's not an option. The app was in an older version (97) but they requested and paid for the upgrade to 2010, so giving them a 2003 version will be about the same as what they had previously.
Thanks for the replies.

maybe it is the client's problem in this case, then. They perhaps need to put this on a machine with dedicated A2010 use only - or accept the changeover process.

You can reassure them it isn't a problem. It's just the way it works.

I suppose they could pay for the launcher I mentioned before, or try and find another one - depends how much of a problem it is.