What changes to I make to a computer that will allow it to run an Access 2003 mde?

[Margaret Bartley]

Where I work, different users have different versions of Access on their
machines. Some users don't have Access installed on their machines at all.

I created some .mdes from Access 2000 .mdbs for the users without Access.
No problem.

My boss, who does not have Access installed, but who has been running my
..mde created by Access 2000, cannot open an .mde that was created by Access
2003.

Also, I find that one of the users, who has Access 97, cannot run any of the
..mdes.

I just convinced them to buy me a spiffy new computer, lots of memory,
loaded for bear, but it came with Office 2003, and I do not have Office 2000
on this machine, so I can't convert me DB to A2K and create the .mde.

How can I create an .mde that my boss, who doesn't even have Access
installed, can run?

I guess, the better question would be:
What do I do to my boss's machine that will allow it to run an Access 2003
mde, once it's run an A2K .mde?

 

[Rick Brandt]

Where I work, different users have different versions of Access on
their machines. Some users don't have Access installed on their
machines at all.
I created some .mdes from Access 2000 .mdbs for the users without
Access. No problem.

My boss, who does not have Access installed, but who has been running
my .mde created by Access 2000, cannot open an .mde that was created
by Access 2003.

Also, I find that one of the users, who has Access 97, cannot run any
of the .mdes.

I just convinced them to buy me a spiffy new computer, lots of memory,
loaded for bear, but it came with Office 2003, and I do not have
Office 2000 on this machine, so I can't convert me DB to A2K and
create the .mde.
How can I create an .mde that my boss, who doesn't even have Access
installed, can run?

I guess, the better question would be:
What do I do to my boss's machine that will allow it to run an
Access 2003 mde, once it's run an A2K .mde?

A user who doesn't have Access at all needs the runtime version of Access
installed regardless of whether they want to run an MDE or an MDB.

Access 97 can only run an Access 97 MDB or MDE

Accesss 2000 can run an Access 97 MDB or and Access 2000 MDB/MDE

Access 2002 and 2003 can run and MDB in Access 97, 2000, or 2002/2003 format and
can run MDEs in either 2000 or 2002/2003 format.

The runtime version has the same restrictions as the licensed versions listed
above.

 

[Guest]

Rick's Information is correct. I would suggest you get your boss to acquire
the 2003 Office Developer's Kit. With it, you will be able to create a
setup.exe file that will install the mde, the 2003 runtime, and any other
support files needed by your application.

 

[Margaret Bartley]

I don't recall doing anything like that with the A2K version, I just created
an .mde, and she was able to run it on her computer. Did someone, earlier,
that she didn't remember, install the runtime version of Access 2000 on her
machine? Or is this a background process that takes care of itself, the
first time, but then I need to do some maintenance when an executable from a
different version of Access in put on the users' machines?

Is this a separate process? I've only ever handed the users the executable,
and never had to worry about installing anything on their machines.

Is there any documentation for this?

Thank you,
Margaret

 

[Guest]

As I remember, the original problem is the diversity of Access versions in
your office. If everyone has the same version of Access, this is not a
problems. With the mix you have, you are going to have errors and problems
and things that don't work correctly.

The solution is to get everyone on the same version of Access. So, that
means you have to purchase a copy of Access 2003 for everybody or you can
purchase the Developers Toolkit. The Toolkit creates a setup.exe file that
includes the runtime version of Access 2003. The setup.exe you build will
include your mdb or mde (preferred), the Access runtime, and any other files
you need to include, such as DLL files needed by your application. This is
the only way you can legally deliver a runtime version of Access.

So, in short, there are two ways:
1. Get every user a copy of Access 2003
2. Get the Developer's Toolkit

 

[Rick Brandt]

I don't recall doing anything like that with the A2K version, I just
created an .mde, and she was able to run it on her computer. Did
someone, earlier, that she didn't remember, install the runtime
version of Access 2000 on her machine? Or is this a background
process that takes care of itself, the first time, but then I need to
do some maintenance when an executable from a different version of
Access in put on the users' machines?

Is this a separate process? I've only ever handed the users the
executable, and never had to worry about installing anything on their
machines.

Is there any documentation for this?

Just making an MDE does not allow a person without Access to use it. The
person you *thought* didn't have Access installed actually did. If they
were able to see the db window then it was not the runtime as the runtime
does not allow that.