I’ve heard it's possible to see an Access database schema even after
converting to an MDE. Is this the case, and if so, is there a way to protect
against this?

Hi, Joe.

> I've heard it's possible to see an Access database schema even after
> converting to an MDE. Is this the case

Yes.

> is there a way to protect
> against this?

Not unless you want to remove the enforcement of relational integrity
between the tables, remove cascade updates and cascade deletes, and remove
all outer joins for tables not explicitly defined in queries. If your
database application needs these relational database structural features,
then leave them as as they are. Otherwise, you can remove all tables and
their relationships from the Relationships window view, but don't re-create
the relationships with VBA code. Then, no one will "see" any relationships.

But to be honest, anyone experienced in relational database design can
easily figure out your schema from watching how your application works, so
you aren't hiding anything if you remove the tables and relationships from
the Relationships window.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Joe Gaines" <(E-Mail Removed)> wrote in message
news:2C8DCFE5-51DB-4697-AE11-(E-Mail Removed)...
> I've heard it's possible to see an Access database schema even after
> converting to an MDE. Is this the case, and if so, is there a way to
protect
> against this?