MDE ?

A

Apprentice

I am developing a database that will be distributed to other States.
Unfortunately there is not a common network. Therefore, I will not be able
to manage or update the MDB. It has to go out in final form and trust me....
I have to test, test and then test again.

That being said, is there a benefit to split or convert to MDE? I don't see
any?

Basically I will be sending out annual upgrades to the database and provide
an import function to bring old data into the new updated db.
 
D

Douglas J. Steele

Splitting and converting to MDE aren't related.

Given your situation, your application really should be split into a
front-end (containing the queries, forms, reports, macros and modules),
linked to a back-end (containing the tables and relations). Do that, and you
won't have to import the data into the new updated database each year.

Whether or not you convert the front-end to an MDE isn't quite as clear cut.
Certainly there are advantages to having using an MDE, but there are also
certain bits of functionality that aren't possible using an MDE since you
cannot open forms or reports in Design view.
 
R

Rick Brandt

Apprentice said:
I am developing a database that will be distributed to other States.
Unfortunately there is not a common network. Therefore, I will not
be able to manage or update the MDB. It has to go out in final form
and trust me.... I have to test, test and then test again.

That being said, is there a benefit to split or convert to MDE? I
don't see any?

Basically I will be sending out annual upgrades to the database and
provide an import function to bring old data into the new updated db.

Splitting would allow you to send users an updated front end without
worrying about their existing data. Don't say you will never want to do
that because "never" happens all the time.

MDE/MDB is up to you. MDEs restrict tampering and are a bit more robust,
but otherwise there would be little difference unless user tampering is an
issue for you.
 
A

Apprentice

Ok, I'll have to read up on the subject. Not sure really how the split works.

Thanks for the advise Doug. I will split the db and learn how it effects etc.
 
D

david

If it is going out to the sales force, an MDE is better.

Sales people get paid on commission, so the sales
reports need to be locked down a little bit. Not a lot,
companies still need double-entry book-keeping, just
enough so that making more sales is easier than re-writing
the sales reports.

(david)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top