Splitting vs MDE

[Jake F]

I finished creating a database that will be used by many people. The
database is in 2002-2003 version but I run it from 2007 just because I've
gotten used to how 2007 operates. I was not able to make and MDE file in
2007 but was able to split the database using 2003. Will it be sufficient
enough to have my tables somewhere else or do I need to figure out an MDE
file so that my modules are blocked as well? Let me know if I'm way off base
here. Thanks.

 

[Klatuu]

In a multi user environment, splitting is an absolute must.
Using an mde would be best, but the file version and the Access version have
to be the same before you can create an mde. In 2007 it is an accde.

Why not just convert everything to 2007?
Are you aware the 2007 Developer's extensions can be downloaded from
Microsoft free? That gives you the ability to create an accde and deliver
the 2007 runtime if you have users that don't have 2007.

 

[John W. Vinson]

I finished creating a database that will be used by many people. The
database is in 2002-2003 version but I run it from 2007 just because I've
gotten used to how 2007 operates. I was not able to make and MDE file in
2007 but was able to split the database using 2003. Will it be sufficient
enough to have my tables somewhere else or do I need to figure out an MDE
file so that my modules are blocked as well? Let me know if I'm way off base
here. Thanks.

Only the frontend will contain any modules (likewise macros, forms, queries
and reports). The backend will contain only the tables, so there's nothing to
block. It can be a .mdb; there's no advantage to making it a .mde.

 

[Tony Toews [MVP]]

I finished creating a database that will be used by many people. The
database is in 2002-2003 version but I run it from 2007 just because I've
gotten used to how 2007 operates. I was not able to make and MDE file in
2007

You will have to convert the MDB into A2007 format before you can make
it an MDE in A2007. However this means that your users will have to
have either A2007 or A2007 runtime installed. They won't be able to
run an A2007 MDE in A2003 or older.

Alternatively you could wander over to a users system with A2003 and
make your MDE there. Then both A2003 and A2007 users could run it.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[John W. Vinson]

John just said there's no advantage. I made a much stronger
statement, one which reflects my impatience with those who try to
use MDEs without first understanding what they are and what they are
useful for.

Point taken... "no advantage" was indeed an understatement.

 

[Steve in MN]

So when you make an MDE file, the only way to "update" the front end is to
make changes in the original file and create a new MDE file?

 

[Arvin Meyer [MVP]]

Yes, that is correct. You can use an automatic updater like Tony Toew's
AutoFE to get the updates automatically:

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