Can Access 2010 Runtime Co-exist with users who already MS Access 2003?

[gphares]

I have a new Application written in MS Access 2010, however, some of my end-users already have the full version of MS Access 2003 or 2007 on their machines.

First, can I install the 2010 run-time version on a user's machine that already has MS Access 2003/2007? Second, how does Access differentiate between the two versions? If there a different "exe" filename?

Thanks

[rpeare]

http://www.pcreview.co.uk/forums/ope...-t3573423.html

Apparently you can do it if you install the run-time components, however one of the respondents notes that if you are switching databases back and for it can take a couple of minutes to re-adjust.

There is also a shortcut remedy to automatically use the /runtime component if your database is the only one they will be opening.

[June7]

Recommendation at http://hitechcoach.com/index.php?opt...tid=7&Itemid=9 is not to have both on same machine probably because of delays caused by re-registration as noted in rpeare's link.

[tanvi]

Whenever you install two versions of MS Access on the same computer (whether it be 97, 2000, 2003, 2007 or 2010), each time you open it, it has to go through some ridiculous 'reconfiguration' which can take a few minutes before you get to designing. I personally would try to keep it on a separate computer since there are a few other caveats even if you get them both running. For example, having 2 versions of MS Access on your computer and you decide to import a form from one mdb to another mdb. After importing that form, if you don't immediately debug/compile (and instead start writing code), you'll undoubtly end up with a corrupt form which will need to be re-imported again. MS Access just doesn't play nice with MS Access on the same computer.