MDE

[mark r]

I guess I do not get the idea of MDE.

I thought, If I created a table of data and a couple of reports in ACCESS
(2000 or 2007) then I could somehow create a runtime version of that table
and report so I
could send the data table to a friend via the internet and he could peruse
the table and report a this leisure.

I thought I could use MDE and then send it to him.

Apart from not understanding how to create the run time version, I am
realizing the friend would have to purchase ACCESS 2007 in order to make the
MDE file work, een if you can teach me to do this.

I figured out how to use snapshot viewer to send him a static picture of the
table, but that is lame.

 

[John W. Vinson]

I guess I do not get the idea of MDE.

I thought, If I created a table of data and a couple of reports in ACCESS
(2000 or 2007) then I could somehow create a runtime version of that table
and report so I
could send the data table to a friend via the internet and he could peruse
the table and report a this leisure.

I thought I could use MDE and then send it to him.

Apart from not understanding how to create the run time version, I am
realizing the friend would have to purchase ACCESS 2007 in order to make the
MDE file work, een if you can teach me to do this.

I figured out how to use snapshot viewer to send him a static picture of the
table, but that is lame.

A MDE is not an executable program. It's a database, just like a .mdb, with no
additional features (in fact it's got all design features and the source code
stripped out). Like a .mdb, it needs some version of Access to use its
features: the forms, reports, etc. are just objects that the MSACCESS.EXE
program can manipulate.

You can obtain a "Runtime" version of Access - for A2007 it's free, but it's
rather pricey for ealier versions. Do a google search for "Access Runtime" for
a plethora of information.

 

[mark r]

John,

I am not very technical. The extent to which I understand the term "run
time" is only as a loadable module. That's it.

Please explain more about this free runtime for A2007 you mentioned.
1. do you mean I can make a table I create able to run on someone else's
laptop even though they don't have ACCESS?
2. how hard is it to learn how to do that
3. links?

 

[Rick Brandt]

John,

I am not very technical. The extent to which I understand the term "run
time" is only as a loadable module. That's it.

Please explain more about this free runtime for A2007 you mentioned. 1.
do you mean I can make a table I create able to run on someone else's
laptop even though they don't have ACCESS? 2. how hard is it to learn
how to do that 3. links?

In Access jargon the runtime IS Access. It's just a version that can
only be used to run files, not create or modify them. It also does not
supply hardly any of the built in interface so to use a file with the
runtime it has to have a form that opens at start-up or a custom main
menu to allow the user to gain access to the various objects. Otherwise
all they see is a blank Access window.

The runtime is intended for use with fully polished applications created
in Access. It is not suitable for people who just want to look at "any
old Access file". In your case if you created a form that opened
automatically at start-up and in that form had some buttons to open the
tables and reports then it would work for you.

 

[John W. Vinson]

John,

I am not very technical. The extent to which I understand the term "run
time" is only as a loadable module. That's it.

Please explain more about this free runtime for A2007 you mentioned.
1. do you mean I can make a table I create able to run on someone else's
laptop even though they don't have ACCESS?
2. how hard is it to learn how to do that
3. links?

Tony Toews has a good summary at
http://www.granite.ab.ca/access/developereditionversions.htm

 

[mark r]

Yeah Rick,

That's what I have been thinking about. Some auto forms and reports,
basically a little user interface would be easy to do. So I am told the
A2007 runtime is free.

1. so what is the link to download the free runtime?
2. to install the free runtime, do i just have to exectue the setup - and do
nothing else?
3. To give my little user interface to my BOSS, don't I have to sort of
COMPILE it? that is what I thought Tools >> Database Utilities> Make a MDE
FILE was for. To compile the user interface along with the table to give to
the user to run on his free runtime. But Vinson says MDE is not for that.
Geeeee, getting an interpretable response and course is like pulling teeth.
Lay it out for heaven sake.
What good is giving someone the tip of an iceberg. Really? A computer
science major of all people should understand that if you can't envision the
beginning, middle and end, you can't make it happen. Like, I am begging here,
as usual for insight, like what else do I have to do to get the skinny? LIKE,
Like. How does it REALLY work to do what I am trying to do. Like. yeah.

 

[Rick Brandt]

Yeah Rick,

That's what I have been thinking about. Some auto forms and reports,
basically a little user interface would be easy to do. So I am told the
A2007 runtime is free.

1. so what is the link to download the free runtime? 2. to install the
free runtime, do i just have to exectue the setup - and do nothing else?

That's it.

3. To give my little user interface to my BOSS, don't I have to sort of
COMPILE it?

Nope. You CAN create an MDE version and give him that, but it is not a
requirement of the runtime.

that is what I thought Tools >> Database Utilities> Make a
MDE FILE was for. To compile the user interface along with the table to
give to the user to run on his free runtime.

Nope. MDE and Runtime are two completely separate concepts.

But Vinson says MDE is not
for that. Geeeee, getting an interpretable response and course is like
pulling teeth. Lay it out for heaven sake.

An MDE is a little smaller, a little faster, handles errors a bit better,
and prohibits viewing/editing of forms, reports, and modules. That is
why people use them. Most people that distribute apps with the Runtime
also want the features of an MDE, but that is coincidental.

What good is giving someone the tip of an iceberg. Really? A computer
science major of all people should understand that if you can't envision
the beginning, middle and end, you can't make it happen. Like, I am
begging here, as usual for insight, like what else do I have to do to
get the skinny? LIKE, Like. How does it REALLY work to do what I am
trying to do. Like. yeah.

Access is not a trivial program to use. It has a learning curve.
Creating apps for other people to use is higher on that curve than
creating things for yourself.

You tell him where to get the 2007 runtime or supply it to him yourself.
He installs that and then he can open your file. What he can DO with
your file once he opens it is up to you.

 

[mark r]

Yeah Rick,

Excellent answer - I can follow that. almost clear.

1. So are these steps correct:
My boss:
1. downloads A2007runtime, runs setup.
2. He actually double clicks the runtime icon and it opens up a RUNTIME
session.
3. He presses File>>OPEN>> and then selects the name of my MDE database,
which he cannot tinker with and mess it up.
4. So I have to copy the MDE FILE to a travel drive to give to my BOSS.
So how does it show up on my C:\ so I can indentify it and copy it to the
travel drive. I am thinking that I copy the FILE FOLDER that contains the
MDE workbase to the travel drive. It does not show up as an .exe file. It
shows up like
my MDB files, just in a windows explorer file folder.
5. I think one reason I think that Tools >> Database Utilities> Make a MDE
FILE
does not work is that when I open up the resultant MDE file and click on a
TABLENAME, I can get to the design view and change things around ---- but
now am thinking that is because I am doing so via ACCESS2002. I think it is
dawning uponme that if I were to close down all my ACCESS windows and OPEN
one from ACCESSRUNTIME2002, then when I open that same MDE file , I will not
be able to get to DESIGN VIEW. Is that right?
6. I have one lap top that has ACCESS2002...how can I upgrade it to 2007 so i
can utlize runtime07? cost $$$ ?
7. How expensive is that ACCESS2002 runtime - amI better off upgrading my
A2002 to A2007 and downloading the runtime for free, strictly comparing
cost, not other features and benefits?

I feel like I am getting somewhere now.

 

[mark r]

great answers
starting to become clear

are these the proper steps
1. My Boss
a. downloads Aruntime2007 and clicks setup
b. opens up an Aruntime2007
c. goes to FILE>>OPEN>> and selects my MDE database (he cant mess it up by
messing up code)
2. how do I give him my MDE database via travel drive?
can I go to windows explorer and copy the FILE FOLDER that contains it to the
travel drive and give him the travel drive?
3. in otherwords, the MDE file is not a standalone *.exe type file. --- I
guess when I copy the MDE databse file folder to the travel drive, it sort of
has the A2007 environment attached, but since he doesn't have A2007, the
RUNTIME2007 lets him open up the database in a limited way.
4. I have a different laptop with A2002. how can I upgrdae it to A2007 so I
can utilize Runtime A2007 for the stuff I build on that laptop? cost $$$?
5. I guess I am thinking that the TOOLS>>DATABASE UTILITIES>>MAKE AN MDE
FILE is not working properly in my A2002 because when I open up the MDE files
I create, I can still get to the DESIGN VIEWS....but that is because I never
purchased ARUNTIME2002 and am opening up those databses using A2002, not a
session of ARUNTIME2002, is that correct? If I opened an A2002 Runtime
session, then I would not be getting at those DESIGN VIEWS...right?

 

[Rick Brandt]

Yeah Rick,

Excellent answer - I can follow that. almost clear.

1. So are these steps correct:
My boss:
1. downloads A2007runtime, runs setup. 2. He actually double clicks the
runtime icon and it opens up a RUNTIME session.

No. Installing the runtime will not create any shortcuts or start menu
items. It also cannot be opened by itself. It can only be opened when a
file to open has already been specified.

3. He presses File>>OPEN>> and then selects the name of my MDE database,
which he cannot tinker with and mess it up.

No, he double clicks your file or you provide a shortcut to your file.
The runtime will have registered itself with Windows as the correct
program to use for MDE files so the runtime will automatically be invoked
any time he double-clicks such a file.

4. So I have to copy the MDE

FILE to a travel drive to give to my BOSS. So how does it show up on my
C:\ so I can indentify it and copy it to the travel drive. I am
thinking that I copy the FILE FOLDER that contains the MDE workbase to
the travel drive. It does not show up as an .exe file. It shows up like
my MDB files, just in a windows explorer file folder.

Would you expect a Word document that you were giving him to be changed
into an exe first? Same with Access. You are giving him a file, not a
program.

5. I think one

reason I think that Tools >> Database Utilities> Make a MDE FILE
does not work is that when I open up the resultant MDE file and click on
a TABLENAME, I can get to the design view and change things around ----

That is expected. MDEs do not prevent design changes to tables and
queries, only to forms, reports, and modules. The runtime will not allow
him to make design changes to your file, but if he were to install full-
blown Access then he could mess with tables and queries.

but now am thinking that is because I am doing so via ACCESS2002. I
think it is dawning uponme that if I were to close down all my ACCESS
windows and OPEN one from ACCESSRUNTIME2002, then when I open that same
MDE file , I will not be able to get to DESIGN VIEW. Is that right?

The runtime does not provide access to the design interface.

6. I

have one lap top that has ACCESS2002...how can I upgrade it to 2007 so
i can utlize runtime07? cost $$$ ?

The Access 2007 runtime will run a 2002 file just fine so you do not need
to upgrade just to have him use the 2007 runtime.

7. How expensive is that ACCESS2002 runtime - amI better off upgrading
my A2002 to A2007 and downloading the runtime for free, strictly
comparing cost, not other features and benefits?

Yes, the 2002 runtime tools would cost you (if you could find them).
2007 is the only one widely available. As stated though you do not need
to upgrade.

 

[mark r]

Thanks again.

<y BOSS uses an APPLE, I guess he could run Windows on his APPLE.
If he can't do that for whatever reason, If I developed my ACCESS table and
queries on Windows Vista, is there some other way to give my BOSS my stuff if
he has an APPLE?

1. Can he download an APPLE version of ARUNTIME2007?
2. Will mACCESS07 database work on his APPLE?
3. etc

That is expected. MDEs do not prevent design changes to tables and
queries, only to forms, reports, and modules. The runtime will not allow
him to make design changes to your file, but if he were to install full-
blown Access then he could mess with tables and queries.

This sounds contradictive.
First you say he can make changes to tables in an MDE, then you say if he
installed dull blown ACCESS, he then could mess with tables.

 

[Rick Brandt]

Thanks again.

<y BOSS uses an APPLE, I guess he could run Windows on his APPLE. If he
can't do that for whatever reason, If I developed my ACCESS table and
queries on Windows Vista, is there some other way to give my BOSS my
stuff if he has an APPLE?

1. Can he download an APPLE version of ARUNTIME2007? 2. Will mACCESS07
database work on his APPLE? 3. etc

He would have to run a Windows emulater. There is no version of Access
that runs on a Mac.

This sounds contradictive.
First you say he can make changes to tables in an MDE, then you say if
he installed dull blown ACCESS, he then could mess with tables.

MDEs prevent design changes to forms, reports, and modules. The runtime
inhibits access to the design view interface of all objects, though
tables and queries can have design changes made via interfaces that the
developer provides.

Thus, if he has only the runtime you could give him an MDE or an MDB and
he would not be able to make design changes using the runtime. If he
later installed a full copy of Access he would be able to change the
design of tables and queries only if you give him an MDE or any object if
you give him an MDB.

 

[Albert D. Kallal]

great answers
starting to become clear

are these the proper steps
1. My Boss
a. downloads Aruntime2007 and clicks setup

Well, if you need word, or excel...you install word or excel.

b. opens up an Aruntime2007

No, you just click on the he excel file or click on the word file, or in
this case the mdb, or mde or accDB file.
You click on it to launch the application.

c. goes to FILE>>OPEN>> and selects my MDE database (he cant mess it up by
messing up code)

You don't have to do the above for word, or excel, or just about any other
software on your computer...so, why change this now??? This works the same
as any other application installed on your computer.

2. how do I give him my MDE database via travel drive?

How do you give him a word file? How do you give him a excel file? how do
you give him any windows file?

This is just windows file, and the process is the same as giving him any
other file.

can I go to windows explorer and copy the FILE FOLDER that contains it to
the
travel drive and give him the travel drive?

Yes. The above sounds good.

3. in otherwords, the MDE file is not a standalone *.exe type file. --- I

Who ever said it was? No one made that suggestion. It does however strip out
the code and design parts of the application (the application part is the
code + forms + reports).

When you take a system like VB6 and create single.exe file, that will NOT
work unless you FIRST install the visual basic runtime system. So, you need
a system in place that can consume that execute file. In the case of VB6
..exe file, you need the VB6 runtimes installed first.

The same goes for mess-access. To use an mdb, or mde file..you need some
system installed on the target machine. That can be the full editing of
ms-access, or the runtime edition (they are almost the same thing...the
runtime edition does have the design tools but other then that..it really
like you are installed ms-access).

guess when I copy the MDE databse file folder to the travel drive, it sort
of
has the A2007 environment attached

No, it does not. That "attachment" you speak of is not different then other
windows file like word, or excel or whatever. There is usually some
application associated with a file extension. That is the ONLY system in
place that allows the person to click on a file and then some application
launches. It is the SAME with word, or excel or access. You have to have
some application installed such as the runtime or full edition. There is no
attachment here of any kind other then that file association.

but since he doesn't have A2007, the
RUNTIME2007 lets him open up the database in a limited way.

No, if he does not have a copy of word, then he can't click on a word file
to launch it ether.

If he does not have full ms-access, or a runtime..then clicking on the file
is the SAME as clicking on a word file on a computer that does not have word
application installed.

4. I have a different laptop with A2002. how can I upgrdae it to A2007 so
I
can utilize Runtime A2007 for the stuff I build on that laptop? cost $$$?

This again is like sending that person a word file. You can have that person
upgrade. And, if your using a newer version of word, then you might have
that person upgrade so they have the same word features. However, the person
already has ms-access installed. In this case you likely best just send that
person a 2002 version of the mdb file. This exactly why access 2003 defaults
to the 2000-2003 mdb format. So, you can in fact send the mdb file to all of
these users across 3 versions. And, the access 2007 runtime can also use a
2000-2003 mdb file. (again, very much like the case for word).

5. I guess I am thinking that the TOOLS>>DATABASE UTILITIES>>MAKE AN MDE
FILE is not working properly in my A2002 because when I open up the MDE
files
I create, I can still get to the DESIGN VIEWS

You can modify the table views and data (else what use would this be if end
users could not modify data!!!).

What they cannot change in a mde is the forms, the code, and the report
layouts. So, they can't change the internal designs of the APPLICATION code.
You need to start thinking from a application point of view. So some objects
such as tables are exposed and can be modified, but then again in MOST cases
we need users to be able to edit data.

So, you can deploy a whole application this way. The user will be prevented
from playing with your forms, reports, code etc (your application part). If
you/they can modify the reports/forms etc, then this is not a mde file, but
is likely a mdb file that bee re-named as a mde file.

....but that is because I never
purchased ARUNTIME2002 and am opening up those databses using A2002, not a
session of ARUNTIME2002, is that correct? If I opened an A2002 Runtime
session, then I would not be getting at those DESIGN VIEWS...right?

No, the issue of design view only locks out forms/reports/code, not the
table designs.....

I explain the runtime for 2007 in details here:
http://www.members.shaw.ca/AlbertKallal//RunTime/Index.html


Also, if you do plan to deploy more then just data to these people, then you
need to read the following article about splitting..as this article ALSO
explains the idea of a mde....

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[David W. Fenton]

The same goes for mess-access.

<giggle>

Yet more evidence that Albert uses Speech Recognition to write his
posts.

 

[Douglas J. Steele]

<giggle>

Yet more evidence that Albert uses Speech Recognition to write his
posts.

What? You don't think he types phonetically?