Re: Database Options - Any other settings I should adjust?

"Steve" <steve@xxxxxxxxxx> wrote in news:fFTMi.4$Wn6.0@xxxxxxxxxxxx:


"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns99BAB33E0BE27f99a49ed1d0c49c5bbb2@xxxxxxxxxxxx
"Steve" <steve@xxxxxxxxxx> wrote in
news:bJuLi.20$gu2.13@xxxxxxxxxxxx:

There are plenty of reasons not to:

1. inability to fix a bug over the phone without sending a new
update, or having the end user edit the MDB and generate a new
MDE. If you've got the MDB on the other end already, you haven't
got too much security.

2. supporting multiple versions of Access. In that case you have
to generate multiple MDEs, one for each version, and that's more
trouble than it's worth.

What kind of security do you think an MDE gets you?


1) I never allow my clients to go in and change code (unless the
client is using there own IT group to maintain and support the
applications). What a potential nightmare.

None of my clients have ever once attempted to intentionally alter
code, except for the clients I was collaborating with (i.e., they
did hired me to enhance the application that they had written and
were continuing to work on).

I also sell an Access based application, and maintain
one code base. I make the fixes, and send the frontend. It
automatically attaches to the backend database (no big deal).

I don't see any of this as relating to the topic of "security."

2) I have no problem generating seperate MDEs for different
versions of Access from one MDB. Not a big deal. For the above
application, the code base is maintain in Access 97. I generate
an Access 97 MDE, Access 2003 MDB and MDE.

Do you automate it?

3) The lack of full-proof MDE security issue is a bogus issue. It
prevents the client from messing with the source code,

Which is only an issue for people who have the class of client for
whom that's a realistic risk -- in my 10+ years of professional
Access development, I've never had such a client.

and provides some level of
security (not great, but better than nothing). Hey, I lock the
door of my house when I leave, even though it is not to tough to
break in. Why make stealing more tempting and easier?

I just don't see delivering an MDE as a security issue unless:

1. you have passwords embedded in your code, AND

2, you have also encrypted your MDE.

I guess if I had many small clients with many different small
applications, the MDE thing could be a pain. But that is not my
business.

Well, it *is* my business, and it *is* a pain.

The point is:

One shouldn't assume that one's situation is universal and make
blanket statements about what every Access developer should do.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: Securing an .MDE
    ... MDE is the same as MDB except the code is precompiled ... If you need more security you can use Workgroup Security, ... I created an .MDE. ... When I launch my .mde, I can still go in and launch the container, ...
    (comp.databases.ms-access)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... I do have both the MDB (on a file server running Win2K server) and the ... MDE. ... I have fixed the problem for an XP Client that is ... Would it help if I zipped up both the mdb and the mde and shipped to you via ...
    (microsoft.public.access.conversion)
  • Re: Can it be that NO ONE HERE knows this answer?
    ... Sounds like you want MDE code (which I presume you control the source code ... otherwise you may want to forget it) to insert/update/delete an MDB ... then would need to build a .net client side application to talk to the web ... possible to link a client side MDE with a WEB server MDB table using ...
    (comp.databases.ms-access)
  • Re: Database Options - Any other settings I should adjust?
    ... or having the end user edit the MDB and generate a new MDE. ... What kind of security do you think an MDE gets you? ... I guess if I had many small clients with many different small applications, ...
    (comp.databases.ms-access)
  • Re: Search Key Not Found Error Again
    ... security to avoid making the issue complicated. ... simply an front end .mde and full global replicas we're ... >MDB was created. ...
    (microsoft.public.access.replication)