Splitting in 2000/2003 environment

[BruceM]

I am ready to split a database, but some computers have Access 2000 and
others have Access 2003. I have Access 2003 on my computer, so I need to
convert a database to 2003 format before I can create an mde file. As I
understand it, Access 2000 machines won't be able to use the file. I'm not
clear on whether I can create an Access 2000 mde and use it with Access
2003.
Joan Wild's site has a process for splitting a secure database (I think I've
seen the procedure elsewhere, too). I gather that it involves copying the
database, removing everything but tables (and relationships) from one of the
copies, removing the tables and relationships from the other ("front end")
copy, and linking the tables in the "front end" copy. An MDE file,
according to Help, does not allow VBA code to be viewed or edited, and
disables the user interface for form and report design (and it does a couple
of other things, I think). With the manually split database, can I get the
same effect as is obtained with an mde by restricting permissions as needed,
password-protecting the VBA code, and setting the startup options so that
the database window is unavailable, etc.?
In other words, does an mde file provide advantages that cannot be obtained
by other means?

 

['69 Camaro]

Hi, Bruce.

I have Access 2003 on my computer, so I need to convert a database to 2003
format before I can create an mde file. As I understand it, Access 2000
machines won't be able to use the file.

Correct. No earlier version of Access can open later versions' database
formats.

I'm not clear on whether I can create an Access 2000 mde and use it with
Access 2003.

Access 2002, 2003, and 2007 can all open Access 2000 MDB's and MDE's.

With the manually split database, can I get the same effect as is obtained
with an mde by restricting permissions as needed, password-protecting the
VBA code, and setting the startup options so that the database window is
unavailable, etc.?

No. It's not equivalent. And don't password protect the VBA code. This
will come back to bite you later more times than not. But even if you you
_did_ password protect the VBA code, the code is still in the file, where a
hex editor can read much of the source code. With an MDE database file, the
source code is removed, so it can't be read with the hex editor.

In other words, does an mde file provide advantages that cannot be
obtained by other means?

Yes. In an MDE database file, forms and reports can't be created or
deleted, and design changes are limited. VBA code can't be changed, added,
or deleted. Libraries are pretty much "set in stone." (There's a
work-around, but that's beyond the scope of a newsgroup post.)

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[BruceM]

Thanks for the reply. That's what I was afraid of. Looks like I'll have to
use a machine with Access 2000 installed so that I can create the necessary
MDE file. In some remote strata of the the organization it was decided that
it isn't necessary to have everybody in the company using the same version
of software a mere 4 years after it came out.

 

['69 Camaro]

Hi, Bruce.

Thanks for the reply.

You're welcome.

In some remote strata of the the organization it was decided that it isn't
necessary to have everybody in the company using the same version of
software a mere 4 years after it came out.

Office 2003 has some features that weren't available when Office 2000 came
out, so it may be necessary to upgrade at least some of the workstations,
but it's very expensive to upgrade the whole enterprise at the same time.
As long as there's one customer who needs Access 2000 MDE's, you'll have
that workstation to create the MDE database files on, so don't get
discouraged.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Tom Wickerath]

splitting is no longer reccomended you should mvoe to ADP

 

[BruceM]

You are incorrect. Furthermore, your advocacy of ADP is a reason to stay
away from it, since you have been wrong about so many things.

 

[Scott McDaniel]

You are incorrect. Furthermore, your advocacy of ADP is a reason to stay
away from it, since you have been wrong about so many things.

As Gunny said, this isn't Tom Wickerath, it's Kempf impersonating him

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[BruceM]

Yes, I'm trying to help out with exposing the fraud and discrediting the
imposter when I can, but Gunny has been most efficient in that regard.