By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,665 Members | 1,761 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,665 IT Pros & Developers. It's quick & easy.

Versions of Access needed A2K MDE? Runtime?

P: n/a
1) Is there a free runtime version of Access available that is more recent
than the one for Access 2000?

2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?

3) If I create a CD using A2K Developer that includes the runtime version of
Access 2K and an installation package, and if someone tries to install the
application from the CD, what happens if someone already has Access 2000 or
a later version on their PC? Does it try to install the runtime anyway or
is it smart enough to know that the runtime will not be needed?

--
Regards,
Peter
Nov 12 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
TC

"wolftor" <wo*****@rogers.com> wrote in message
news:Sm*******************@news01.bloor.is.net.cab le.rogers.com...
1) Is there a free runtime version of Access available that is more recent than the one for Access 2000?
AFAIK, there has never been, and never will be, a "free" version of the
Access runtime.

2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?
I don't have Access here to check, but from memory, I believe the online
help for Access 97 specifically stated that MDEs would not work on future
versions. It's unlikely that this rule will change, IMO.

3) If I create a CD using A2K Developer that includes the runtime version of Access 2K and an installation package, and if someone tries to install the
application from the CD, what happens if someone already has Access 2000 or a later version on their PC? Does it try to install the runtime anyway or
is it smart enough to know that the runtime will not be needed?
Don't know.

HTH,
TC


--
Regards,
Peter


Nov 12 '05 #2

P: n/a
To your last question -
If you run an installation package which includes a runtime on a machine
where that version of Access is already installed, the runtime will not be
installed.
If however, for instance, you run a package with A2K runtime on a
machine where Access 97 is already installed, A2K runtime *will* be
installed.

HTH
- Turtle

"wolftor" <wo*****@rogers.com> wrote in message
news:Sm*******************@news01.bloor.is.net.cab le.rogers.com...
1) Is there a free runtime version of Access available that is more recent than the one for Access 2000?

2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?

3) If I create a CD using A2K Developer that includes the runtime version of Access 2K and an installation package, and if someone tries to install the
application from the CD, what happens if someone already has Access 2000 or a later version on their PC? Does it try to install the runtime anyway or
is it smart enough to know that the runtime will not be needed?

--
Regards,
Peter

Nov 12 '05 #3

P: n/a
"MacDermott" <ma********@nospam.com> wrote in message
news:bu*****************@newsread2.news.atl.earthl ink.net...
To your last question -
If you run an installation package which includes a runtime on a machine
where that version of Access is already installed, the runtime will not be
installed. [snip]


That's not exactly correct. The Runtime "environment" is installed regardless
of whether the licensed product already exists or not. It just uses the
existing folder locations when a licensed version is present. Additionally; if
the Access executable in your Runtime package is newer than the one already
present the existing one is replaced.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #4

P: n/a
Does anyone know the answers to questions 1 & 2?
Also, If I create my mde in Access97 (still my favorite version because of
how simple it is to double click on a subform to open that subform), and
package it with the runtime, will the app work if the user has other
versions of Access (or no Access at all) and other versions of Windows than
was used for packaging?
"wolftor" <wo*****@rogers.com> wrote in message
news:Sm*******************@news01.bloor.is.net.cab le.rogers.com...
1) Is there a free runtime version of Access available that is more recent
than the one for Access 2000?

2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?

3) If I create a CD using A2K Developer that includes the runtime version of
Access 2K and an installation package, and if someone tries to install the
application from the CD, what happens if someone already has Access 2000 or
a later version on their PC? Does it try to install the runtime anyway or
is it smart enough to know that the runtime will not be needed?

--
Regards,
Peter

Nov 12 '05 #5

P: n/a
wolftor previously wrote:
1) Is there a free runtime version of Access available that is more
recent
than the one for Access 2000?
No version of the Access runtime has ever been free.
If you are using a 'free' version then you are using an unlicensed
version.
2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?


Probably, if it doesn't include references for other products.
(All can only be 2002 and 2003 - who knows what will happen after that)

Regards

Peter Russell
Nov 12 '05 #6

P: n/a
SA
A2000 mdes are able to be run currently in Access 2002 (Xp) and in Access
2003; they all use the Jet 4.0 engine....
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"Peter Russell" <ru***@127.0.0.1> wrote in message
news:me**********************@russellscott.btinter net.com...
wolftor previously wrote:
1) Is there a free runtime version of Access available that is more
recent
than the one for Access 2000?


No version of the Access runtime has ever been free.
If you are using a 'free' version then you are using an unlicensed
version.
2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?


Probably, if it doesn't include references for other products.
(All can only be 2002 and 2003 - who knows what will happen after that)

Regards

Peter Russell

Nov 12 '05 #7

P: n/a
Perhaps I'm not clear on just what you mean by the runtime "environment".

I don't have direct access to the client sites at this point, but I'm pretty
sure I've had sites where the full Access 97 and the Runtime Access 2000
co-existed.

As I understand what you're describing, if for example a full version of A2K
was installed on a PC, and I executed an install package with A2K runtime,
the full version would be disabled and only the runtime would work. That
would not make me a happy customer.

Is there something I'm misunderstanding here?
- Turtle

"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:bp*************@ID-98015.news.uni-berlin.de...
"MacDermott" <ma********@nospam.com> wrote in message
news:bu*****************@newsread2.news.atl.earthl ink.net...
To your last question -
If you run an installation package which includes a runtime on a machine where that version of Access is already installed, the runtime will not be installed. [snip]
That's not exactly correct. The Runtime "environment" is installed

regardless of whether the licensed product already exists or not. It just uses the
existing folder locations when a licensed version is present. Additionally; if the Access executable in your Runtime package is newer than the one already present the existing one is replaced.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 12 '05 #8

P: n/a
"MacDermott" <ma********@nospam.com> wrote in message
news:_q****************@newsread1.news.atl.earthli nk.net...
Perhaps I'm not clear on just what you mean by the runtime "environment".

I don't have direct access to the client sites at this point, but I'm pretty
sure I've had sites where the full Access 97 and the Runtime Access 2000
co-existed.

As I understand what you're describing, if for example a full version of A2K
was installed on a PC, and I executed an install package with A2K runtime,
the full version would be disabled and only the runtime would work. That
would not make me a happy customer.

Is there something I'm misunderstanding here?
- Turtle


I didn't mean to imply that the installation of the Runtime would disable the
licensed version. Only that it still gets installed.

If the setup program sees no licensed installation of Access then it installs
itself in a subfolder of the application being installed. If it sees there is a
licensed version installed it uses that existing folder location instead. It
will still replace any files in the existing Office folder that are older
versions than that being installed by the Runtime (including the Access
executable) and it will install the files and registry entries to support the
Runtime. On such a machine for example the /Runtime switch can be used whereas
on a machine with only the licensed version it cannot (unless its the
Developer's Edition).

Mind you, I have seen the scenario you describe above under certain
circumstances.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #9

P: n/a
TC

"wolftor" <wo*****@rogers.com> wrote in message
news:8P******************@news04.bloor.is.net.cabl e.rogers.com...

(SNIP)
Does anyone know the answers to questions 1 & 2?

Yes, I gave them to you. Did you not see them?

TC

Nov 12 '05 #10

P: n/a
TC
But I believe the policy is, an MDE will not >necessarily< run on every
higher version of Access.

The issue is surely not the version of Jet; it is the version of the
compiled sourcecode.

No? Yes?

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
A2000 mdes are able to be run currently in Access 2002 (Xp) and in Access
2003; they all use the Jet 4.0 engine....
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"Peter Russell" <ru***@127.0.0.1> wrote in message
news:me**********************@russellscott.btinter net.com...
wolftor previously wrote:
1) Is there a free runtime version of Access available that is more
recent
than the one for Access 2000?


No version of the Access runtime has ever been free.
If you are using a 'free' version then you are using an unlicensed
version.
2) If I create an application (MDE) in A2K, will it run on all later
versions of Access?


Probably, if it doesn't include references for other products.
(All can only be 2002 and 2003 - who knows what will happen after that)

Regards

Peter Russell


Nov 12 '05 #11

P: n/a
SA
TC:

If you've opened a copy of Access 2002 or 2003 lately you'll find that they
know how to read A2000 formatted dbs, mdb, or mde. Heck you can even
reference an A2000 mde from an A2K2 mdb without problem.
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"TC" <a@b.c.d> wrote in message news:1069030712.627435@teuthos...
But I believe the policy is, an MDE will not >necessarily< run on every
higher version of Access.

The issue is surely not the version of Jet; it is the version of the
compiled sourcecode.

No? Yes?

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
A2000 mdes are able to be run currently in Access 2002 (Xp) and in Access 2003; they all use the Jet 4.0 engine....
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"Peter Russell" <ru***@127.0.0.1> wrote in message
news:me**********************@russellscott.btinter net.com...
wolftor previously wrote:

> 1) Is there a free runtime version of Access available that is more
> recent
> than the one for Access 2000?

No version of the Access runtime has ever been free.
If you are using a 'free' version then you are using an unlicensed
version.

> 2) If I create an application (MDE) in A2K, will it run on all later
> versions of Access?

Probably, if it doesn't include references for other products.
(All can only be 2002 and 2003 - who knows what will happen after that)
Regards

Peter Russell



Nov 12 '05 #12

P: n/a
TC
Thanks Steve, I didn't know that. So just to be sure: is it now >policy<
that an MDE created with or after A2k, will >definitely< run on all future
versions of Access? Or is that just what happens at present, with the
current versions > 97? Is there anything in the online help on that? (Sorry
to ask, but I do not have A2k+ available, at all, at present.)

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
TC:

If you've opened a copy of Access 2002 or 2003 lately you'll find that they know how to read A2000 formatted dbs, mdb, or mde. Heck you can even
reference an A2000 mde from an A2K2 mdb without problem.
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"TC" <a@b.c.d> wrote in message news:1069030712.627435@teuthos...
But I believe the policy is, an MDE will not >necessarily< run on every
higher version of Access.

The issue is surely not the version of Jet; it is the version of the
compiled sourcecode.

No? Yes?

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
A2000 mdes are able to be run currently in Access 2002 (Xp) and in Access 2003; they all use the Jet 4.0 engine....
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"Peter Russell" <ru***@127.0.0.1> wrote in message
news:me**********************@russellscott.btinter net.com...
> wolftor previously wrote:
>
> > 1) Is there a free runtime version of Access available that is more > > recent
> > than the one for Access 2000?
>
> No version of the Access runtime has ever been free.
> If you are using a 'free' version then you are using an unlicensed
> version.
>
> > 2) If I create an application (MDE) in A2K, will it run on all later > > versions of Access?
>
> Probably, if it doesn't include references for other products.
> (All can only be 2002 and 2003 - who knows what will happen after that) >
> Regards
>
> Peter Russell



Nov 12 '05 #13

P: n/a
I'm relatively sure that neither Microsoft nor any other corporation would
make such an open-ended promise. Access 2002 and Access 2003, by default,
save in Access 2000 file-format, so can run it.

I was not, and am not, convinced that an MDE made with Access 2002/3 can be
run by an earlier version.

Larry Linson
Microsoft Access MVP

"TC" <a@b.c.d> wrote in message news:1069121262.704056@teuthos...
Thanks Steve, I didn't know that. So just to be sure: is it now >policy<
that an MDE created with or after A2k, will >definitely< run on all future
versions of Access? Or is that just what happens at present, with the
current versions > 97? Is there anything in the online help on that? (Sorry to ask, but I do not have A2k+ available, at all, at present.)

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
TC:

If you've opened a copy of Access 2002 or 2003 lately you'll find that

they
know how to read A2000 formatted dbs, mdb, or mde. Heck you can even
reference an A2000 mde from an A2K2 mdb without problem.
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"TC" <a@b.c.d> wrote in message news:1069030712.627435@teuthos...
But I believe the policy is, an MDE will not >necessarily< run on every higher version of Access.

The issue is surely not the version of Jet; it is the version of the
compiled sourcecode.

No? Yes?

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
> A2000 mdes are able to be run currently in Access 2002 (Xp) and in

Access
> 2003; they all use the Jet 4.0 engine....
> --
> Steve Arbaugh
> ACG Soft
> http://ourworld.compuserve.com/homepages/attac-cg
>
> "Peter Russell" <ru***@127.0.0.1> wrote in message
> news:me**********************@russellscott.btinter net.com...
> > wolftor previously wrote:
> >
> > > 1) Is there a free runtime version of Access available that is more > > > recent
> > > than the one for Access 2000?
> >
> > No version of the Access runtime has ever been free.
> > If you are using a 'free' version then you are using an unlicensed
> > version.
> >
> > > 2) If I create an application (MDE) in A2K, will it run on all later > > > versions of Access?
> >
> > Probably, if it doesn't include references for other products.
> > (All can only be 2002 and 2003 - who knows what will happen after

that)
> >
> > Regards
> >
> > Peter Russell
>
>



Nov 12 '05 #14

P: n/a
TC
> I was not, and am not, convinced that an MDE made with Access 2002/3 can
be run by an earlier version.

Larry, it would clearly be unsafe to assume that an MDE from any version,
would run in any earlier version. The later version would have new
constructus, requiring new opcodes (or whatever) in the MDE interpreter.
Those opcodes would not be recognized by earlier versions. There's no future
in wondering whether later version MDEs will ever run in earlier versions.

The question is, will >earlier< versions always run in >later< versions?

Personally, I have never seen any good explanation of why they should not.
However, I recall from A97 help, a clear statement that MDEs >will not< run
in later versions.

I gather that now, an A2k MDE will run in AXP. But is that by chance, or
does it represent a change of policy, or is it that no relevant changes were
made between the two versions? No-one seems to be asking that question.

When I create a new build of my product, I include a seperate MDE for each
version of Access that it supports: currently A97, A2k and AXP. My
installation program checks the version of Access on the user's PC, &
installs the corresponding MDE.

If the new rule is that MDEs will >definitely< run on future versions of
Access, then clearly, I only need two MDEs - one for A97, another for all
versions thereafer. But if that is >not< the new rule - and it only happens
at present "by chance" - then I'll stick with having a seperate MDE per
version.

It surprises me that this doesn't seem to have raised any interest. I design
my product based on what I know (or think I know!) >for sure<, not on things
I notice which might just be coincidence, or random hapennings.

So I am looking for a definitive statement, from someone, as to whether
there has been a change of policy regading upwards-compatibility of MDEs.
There can only be three answers to that:

- Yes, they are guaranteed to be upwards compatible from A2k onwards
(barring "acts of god", of course);

- No, they are >NOT< garanteed to be upwards compatible at all; it just
happens that A2k ones will run on AXP, but no-one should jump to conclusions
from that; or,

- We neither know, nor care. (A strange response, IMO, for anyone who
distributes a professional product.)

Cheers,
TC
"Larry Linson" <bo*****@localhost.not> wrote in message
news:Eu******************@nwrddc02.gnilink.net...
I'm relatively sure that neither Microsoft nor any other corporation would
make such an open-ended promise. Access 2002 and Access 2003, by default,
save in Access 2000 file-format, so can run it.

I was not, and am not, convinced that an MDE made with Access 2002/3 can be run by an earlier version.

Larry Linson
Microsoft Access MVP

"TC" <a@b.c.d> wrote in message news:1069121262.704056@teuthos...
Thanks Steve, I didn't know that. So just to be sure: is it now >policy<
that an MDE created with or after A2k, will >definitely< run on all future
versions of Access? Or is that just what happens at present, with the
current versions > 97? Is there anything in the online help on that?

(Sorry
to ask, but I do not have A2k+ available, at all, at present.)

TC
"SA" <~f***********@nspm.com> wrote in message
news:bp**********@ngspool-d02.news.aol.com...
TC:

If you've opened a copy of Access 2002 or 2003 lately you'll find that

they
know how to read A2000 formatted dbs, mdb, or mde. Heck you can even
reference an A2000 mde from an A2K2 mdb without problem.
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"TC" <a@b.c.d> wrote in message news:1069030712.627435@teuthos...
> But I believe the policy is, an MDE will not >necessarily< run on every > higher version of Access.
>
> The issue is surely not the version of Jet; it is the version of the
> compiled sourcecode.
>
> No? Yes?
>
> TC
>
>
> "SA" <~f***********@nspm.com> wrote in message
> news:bp**********@ngspool-d02.news.aol.com...
> > A2000 mdes are able to be run currently in Access 2002 (Xp) and in
Access
> > 2003; they all use the Jet 4.0 engine....
> > --
> > Steve Arbaugh
> > ACG Soft
> > http://ourworld.compuserve.com/homepages/attac-cg
> >
> > "Peter Russell" <ru***@127.0.0.1> wrote in message
> > news:me**********************@russellscott.btinter net.com...
> > > wolftor previously wrote:
> > >
> > > > 1) Is there a free runtime version of Access available that is more
> > > > recent
> > > > than the one for Access 2000?
> > >
> > > No version of the Access runtime has ever been free.
> > > If you are using a 'free' version then you are using an

unlicensed > > > version.
> > >
> > > > 2) If I create an application (MDE) in A2K, will it run on all

later
> > > > versions of Access?
> > >
> > > Probably, if it doesn't include references for other products.
> > > (All can only be 2002 and 2003 - who knows what will happen after that)
> > >
> > > Regards
> > >
> > > Peter Russell
> >
> >
>
>



Nov 12 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.