MDE Files

[Barry]

Hello,

I have a database split into a front end and a back end,
with the front end an .mde file. I was wondering: should
the back end be an .mdb file, or an .mde? I was thinking
one advantage of the latter is that it would prevent a
user who opens the back end from creating new forms.
Thanks in advance to anyone who replies.

 

[Bruce M. Thompson]

I have a database split into a front end and a back end,

with the front end an .mde file. I was wondering: should
the back end be an .mdb file, or an .mde? I was thinking
one advantage of the latter is that it would prevent a
user who opens the back end from creating new forms.
Thanks in advance to anyone who replies.

Normally, since creating an MDE file has no advantages for protecting tables,
one would leave the back-end in MDB format. If you are having troubles with
users creating forms, or other code-capable objects, in the back-end, however,
converting the file to an MDE might just be the simplest way to control this.
Beyond that, one would need to consider Access user-level security to help
prevent *any* unauthorized modifications to the back-end data file. If it
reaches that point, obtain a copy of the Access Security FAQ for guidance in
securing your file. The FAQ is available at
http://support.microsoft.com/default.aspx?kbid=207793.

 

[Barry]

Bruce, thanks very much for your insight. That was very
helpful.

Barry