Running Multiple Runtime Versions?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

ljr - 21 Aug 2007 14:58 GMT

I currently develop small applications using A2003 using a 2000 format for
the users, who do not have access at all. I have run into alot of reference
problems and it's a headache. I am considering an upgrade on my machine to
A2007 with runtime extensions. I was curious about users who are currently
running 2000 runtime apps and the possiblility of running apps written with
A2007. What problems will I run into? Will distributing the 2007 runtime
with my app produce errors when user opens a 2000 runtime app? In other
words, some users will have multipe apps using differnt runtimes.

Thanks

Reply to this Message

Tony Toews [MVP] - 21 Aug 2007 19:14 GMT

>I currently develop small applications using A2003 using a 2000 format for
>the users, who do not have access at all. I have run into alot of reference
>problems and it's a headache.

What kind of reference problems? Do you have references you really
don't need? Or, for example, are you using the Calendar control which
can be replaced with an API call or Access forms?

> I am considering an upgrade on my machine to
>A2007 with runtime extensions. I was curious about users who are currently
>running 2000 runtime apps and the possiblility of running apps written with
>A2007. What problems will I run into? Will distributing the 2007 runtime
>with my app produce errors when user opens a 2000 runtime app? In other
>words, some users will have multipe apps using differnt runtimes.

This is going to be a PITA and/or very difficult from the users
viewpoint. The problem is that shortcuts are created by the runtime
has just the database name including the .mdb extension. So now
which version of Access will run the MDB? The last one executed.
That's fine when it's the A2007. But not so fine when A2000 attempts
to open an A2000 MDB.

Tony

Signature

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Reply to this Message

SteveM - 21 Aug 2007 21:10 GMT

You can resolve some issues by specifying the actual version of MSACCESS.EXE
to run in the shortcut properties. I invested in the SageKey runtime
installer some time ago and have had complete success with it up to now, even
with different versions of Access on the same machine.

Steve

> I currently develop small applications using A2003 using a 2000 format for
> the users, who do not have access at all. I have run into alot of reference
[quoted text clipped - 6 lines]
>
> Thanks

Reply to this Message

Jose Perdigao - 30 Sep 2007 15:12 GMT

Hi Steve,
The sagekey product, solve the problem about windows installer messages
wnhem you pass from one application access 2007 to acc2003?
They have a trial?
Thanks

> You can resolve some issues by specifying the actual version of MSACCESS.EXE
> to run in the shortcut properties. I invested in the SageKey runtime
[quoted text clipped - 13 lines]
> >
> > Thanks

Reply to this Message