Access 2007 Compatability with Access 2002 Runtime

[Guest]

I have some legacy software that runs under Access 2002 Runtime. I am
currently testing Access2007 Beta 2 on a development system on which I have
also installed Access Runtime 2002.
Does anyone know where I can possibly find a list of backwards compatability
issues for Access 2007?
The VBA code is failing in places where it never has before.
I understand Beta's can be a little quirksome but I am not sure if the issue
is related to Beta or backwards compatablility.
It may be an issue of two versions on the same platform?
Thanks in advance.

 

[Albert D. Kallal]

You can actually run 25 year old software on a brand new pc.

You can run a 10, or 15 year old version of ms-access on a brand new pc.

However, you can't run access 97 on a 1981 pc (that pc did not even have a
mouse).

and, during the above period, companies like apple have forced you to throw
out software on more then one occasions. So, if you want to run and use 15
year old DOS based version of software to develop with, you can. Microsoft
has the best track record in this regards by a country mile.

If you want to run the original 1981 Visi-Calc spreadsheet on a BRAND NEW
windows xp box, you can. There is a copy here:

http://www.bricklin.com/history/vcexecutable.htm

So, from a compatibility point of view, vendors like Apple don't allow you
to run old software, yet MS does.

However, I NEVER been aware in that last 25 year period that you could take
new version of software data, and use it with a previous version? I cant
think of any precedent here.

So, in your case, I never been aware that you can mix the runtime with
different versions of ms-access. (it turns out you can do this in some
cases..but, I don't recommend).

So, if 25 years of the pc computer industry has any hint, or lesson, it is
usually that you can't mix a new version of something with old parts of a
previous version.

You certainly can't use a access 97 mde with a2003. And, you certainly can't
use the a97 runtime for a2003 stuff either. This is not new news here.

I am not sure if you given the past history of computers some thought on the
above issues, but as a general rule, you can move forward. (perhaps you are
new to computers, or very recently learned about them). if you been around
computers, then give the above compatibility issues some thought, and you
generally conclude the same thing I have as above...

So, it likely is a rare day indeed that you can use a old runtime with newer
version of software. I think you will have to wait for the a2007 runtime to
be released.

I can't imagine trying to mix and match runtimes with different versions of
ms-access. You do realize that the runtime is really the same thing as the
full version of ms-access? (and thus the SAME problems exist when trying to
mix things).

 

[Patrice]

Don't know at which step they are regarding documentation but this should be
listed in the help for the final version as it was for previous releases...

Else seeing what fails hsould overtime gives an idea (is this mising
features from vBA, because it's not VBA or some external reasons such as
using now a bad parth or something...)

 

[Guest]

Thanks for the information. Actually I understand exactly what you are
talking about, However I may have misstated my original question.
What I am trying to find out is:
Can you run Access 2007 on a system that is also running an older version of
MSAccess.
I have an application that is distribuated with Access Runtime 2002. The
VBA code was written in Access 2002.
Can an Access 2002 application and runtime 2002 co-exist on a platform also
running Access 2007 without stepping all over each other.
I have seen a few references where the 2007 installation is not compatable
with other versions of Access.

I am not trying to run the Access 2002 application with Access 2007.

Thanks
Tim

 

[Granny Spitz via AccessMonster.com]

I think you will have to wait for the a2007 runtime to
be released.

I think the beta version already has been. I don't know which file it's in
though.

VSTO 2005 SE for Office 2007 beta:
http://www.microsoft.com/downloads/...73-0D84-4E39-983C-CA22F2107B07&displaylang=en


VSTO 2005 SE for Office 2007 Runtime beta (for Office solutions):
http://www.microsoft.com/downloads/...d2-fc62-4a44-82cb-ae73c2fc7146&displaylang=en


Don't install these betas with more than one version of Office. Install with
either Office 2003 or Office 2007 beta.

 

[Albert D. Kallal]

ah..ok.... (I did miss your question then..sorry).

There are quite a few members here that actually are running 3, or even 4
versions of ms-access on the SAME machine.

So, as general rule, you can run multiple versions on the same machine.

If you go back to a2000 (or earlier), and used the default install, then you
create a supreme mess, as you have littler 1000's of dlls from both program
MIXED INTO THE SAME directory. Not only would this effectively trash your
ms-access install, but nearly mess your machine up.

Since a2002 the install always goes to its own directory. (and thus, in
theory, a2000 is ok..since it is the last version that did not choose a
directory different by default).

For previous versions, you simply choose custom install, and thus are given
the opportunity to choose the directory where the install goes.

So, if you are running a2002 and later, you likely can simply use the
defaults, and install 2002, 2003, and 2007 all on the same machine without
problems. In fact, you could also install 2000 also. (it was only from 2000
backwards that you had to choose custom install to prevent problems).

So, yes..you should have little, if any problems running 2, or 3 versions.
There are few annoyances (for example, the mdb file association is set to
the LAST version you run - and, ms-access (and you) don't know what the file
format (extension) is, so you have to group your files in directories, or
always use a full shortcut to launch the file.

That means if you run the "runtime" mdb...then all mdb file assocations are
now a2002 runtime. If you run a2007, and open a mdb, then all file
associations are now a2007 (including your existing runtime mdb's... - but,
they likey have a shortcut).

I would not install the 2007 beta on a pc that matters, or is in use. (it is
beta, and subject to causing problems on your machine). Do note that virtual
pc is now free, and that would be my sugestion to run a2007.

So, in theory, you can do this, but you also are installing a beta, and that
has no place on a production machine, but ONLY on a machine you are willing
to suffer instability etc. Note that the above advice applies to running
more then one version of the runtime on a pc.