MDB vs MDE

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

SteveC - 19 Jun 2006 03:10 GMT

I suppose MDE is standalone so user doesn't need Access loaded on the PC.
My questions:

1)Can you still edit the database properties and add tables and forms, etc?
2) Can you convert MDE back to MDB

I am learning Access with 2007 Beta version. I've had some trouble; mostly
with it telling me when I try to break or edit a relationship that I have No
Delete Permissions on MSysObjects. I have gotten around this by renaming
the tables and using them for somehting else with the same relationship
(basically the ItemID that I am working with as).

I know I am learning this the hard way, but I am getting there. I am on
version 14 of my database and it mostly works! Thanks! I have other
questions I will post later. I do search for the answers first so I don't
come here except as last resort.

Reply to this Message

John Vinson - 19 Jun 2006 03:58 GMT

>I suppose MDE is standalone so user doesn't need Access loaded on the PC.

You suppose incorrectly. An MDE, just like a MDB, requires (some
version of) Access in order to run it. You can purchase the
variously-named Access Developers Edition which allows you to
distribute an Access Runtime, which can open a MDE or a MDB file.

>My questions:
>
>1)Can you still edit the database properties and add tables and forms, etc?

Only in a VERY limited way; essentially - no, you cannot. For one
thing, all the source code of your VBA routines is GONE; it no longer
exists in the database, period.

>2) Can you convert MDE back to MDB

No. You must keep the MDB around.

A MDE file exists primarily so that you can distribute a database in a
form that users CANNOT modify, and so that you can keep your code
private. It is *not* an executable program; it's still a database, a
crippled database at that.

>I am learning Access with 2007 Beta version. I've had some trouble; mostly
>with it telling me when I try to break or edit a relationship that I have No
>Delete Permissions on MSysObjects. I have gotten around this by renaming
>the tables and using them for somehting else with the same relationship
>(basically the ItemID that I am working with as).

Note that this is *BETA SOFTWARE* - meaning it is *known* to still
have bugs, and not to be fully supported. That's why it's called "beta
testing" - it is not the released product, it's being tested (on you!)

>I know I am learning this the hard way, but I am getting there. I am on
>version 14 of my database and it mostly works! Thanks! I have other
>questions I will post later. I do search for the answers first so I don't
>come here except as last resort.

We'll be glad to help, especially if you've done your homework as you
suggest!

John W. Vinson[MVP]

Reply to this Message

SteveC - 19 Jun 2006 16:06 GMT

LOL; I am glad I posted as my supposition (guess) was so wrong. I will stay
away from MDE then. It seems only right that I should learn on a buggy
version of Access since my knowledge of it is even buggier.

>>I suppose MDE is standalone so user doesn't need Access loaded on the PC.
>
[quoted text clipped - 42 lines]
>
> John W. Vinson[MVP]

Reply to this Message