Quick Questions About Creating an MDE

[Robert T]

I want to make a simple database for my neighbor who does contracting work.
The purpose of the application is to track her expenses and allow her to bill
clients for her services. I've never created nor used an MDE, so I'm only
guessing this is what we should use.

1. For many years I've used a fabulous database program called Alpha Five to
create applications for others with the company's RunTime. One of the many
positives about using the RunTime is the fact that the user doesn't need to
purchase Alpha Five.

Is this also true if I create an MDE for my neighbor? Can she run the
application even if she doesn't have Access 2003?

2. I read somewhere in this forum that MDE files should be split into a
Front and Back End. Do you agree? If so, please explain why.

3. Are there any caveats or warnings I should be aware of before attempting
to design my first MDE with Access 2003?

Thanks,
Robert

 

[Maurice]

Hi Robert,

You should make a distinction in runtime and mde. reading your post'i'm
guessing you are talking about a runtime version.

An mde is a version where the modules are encrypted and you cannot make any
changes anymore. If you do need to make changes you have to make those in the
original mdb file.

If you need to create a db for using without Microsoft Access you need to
make a runtime version. If you create a runtime version your neighbour
doesn't need office.

To create runtimes for office 2003 you need a copy of visual studio which
allows you to make runtimes. Office 2007 makes it possible to create runtimes
without the need for visual studio. So be prepared for additional costs when
creating runtimes in office 2003.

hopes this gives you some insight into what you are looking for.

 

[Jerry Whittle]

1. An MDE won't run without Access. For that you need the runtime version.

Check out Tony Toews comments:

http://www.granite.ab.ca/access/developereditionfaq.htm

It isn't cheap (unless you are using Access 2007) but you can convert a db
that you develop into a runtime version that everyone will be able to use
even without the full MS Access program installed.

2. Just because! ;-) There are many reasons; however, if the database is
going to be used by ONLY one person, you could consider not creating a
BE..... except if you are making it a MDE then there will be no way to make
changes to the database and the tables will be trapped inside of that file.
You would need to export all the data out of it into the new MDE.

3. Keep the source MDB file handy and give a copy of it to your client.
Otherwise there is no way to make changes to the forms, reports, code, etc.

In a nutshell if your goal is to create something that your neighbor can run
without having Access 2003 installed, don't bother. It will probably be more
expensive and time consuming.

In fact your client might be better served with a commerical product such as
Quickbook or Money. It's going to be expensive at first but cheaper than
building a custom database.

 

[Rick Brandt]

I want to make a simple database for my neighbor who does contracting
work. The purpose of the application is to track her expenses and
allow her to bill clients for her services. I've never created nor
used an MDE, so I'm only guessing this is what we should use.

1. For many years I've used a fabulous database program called Alpha
Five to create applications for others with the company's RunTime.
One of the many positives about using the RunTime is the fact that
the user doesn't need to purchase Alpha Five.

Is this also true if I create an MDE for my neighbor? Can she run the
application even if she doesn't have Access 2003?

There is an Access runtime, but it is not just converting to an MDE. It's a
separate product that you (the developer) obtain and then distribute to your
users. Costs them nothing, but costs you extra unless you are using Access
2007 because the runtime is free for that version.

You cannot run just "any old Access file" with the runtime though. It needs
to be a fully developed application because the runtime does not provide
most of the Access interface.

2. I read somewhere in this forum that MDE files should be split into
a Front and Back End. Do you agree? If so, please explain why.

What you read is that ALL multi-user apps should be split. Again, a
completely separate concept from an MDE.

3. Are there any caveats or warnings I should be aware of before
attempting to design my first MDE with Access 2003?

Your don't design an MDE. You design an MDB and then create an MDE from it
which you distribute to users. Those users either need to have Access or
the runtime (just as they would if you gave them an MDB). Almost all of the
caveats are for the runtime. There are virtually no caveats to an MDE other
than the users cannot make design changes to code-based objects (forms,
reports, modules).

 

[rrabins30]

I want to make a simple database for my neighbor who does contracting work..
The purpose of the application is to track her expenses and allow her to bill
clients for her services. I've never created nor used an MDE, so I'm only
guessing this is what we should use.

1. For many years I've used a fabulous database program calledAlphaFiveto
create applications for others with the company's RunTime. One of the many
positives about using the RunTime is the fact that the user doesn't need to
purchaseAlphaFive.

Is this also true if I create an MDE for my neighbor? Can she run the
application even if she doesn't have Access 2003?

2. I read somewhere in this forum that MDE files should be split into a
Front and Back End. Do you agree? If so, please explain why.

3. Are there any caveats or warnings I should be aware of before attempting
to design my first MDE with Access 2003?

Thanks,
Robert

Our product was mentioned on this forum so i thought i would jump in.
Alpha Five (www.alphasoftware.com) is similar to MS Access in that it
lets you build custom desktop apps - it is pretty agnostic about using
its built in database engine or it has direct drivers for building
apps against MS Access, Oracle, SQL Server, DB2, Postgres, QuickBooks,
Paradox, Oracle Lite, Sybase. It does have a runtime as described
above which does not require the user of an app to have Alpha Five.
The other factor (and appeal) is that Alpha Five ALSO lets you build
complete web apps with reporting, security and AJAX - similar to what
you can do with PHP or Visual Studio .Net, but in a lot less time and
more easily. More info relative to MS Access is at http://www.alphafivedatabase.com/access/

Thanks
Richard Rabins
(e-mail address removed)