what do you do about code? mde or not

If you created a database application for somebody, do you send the mde only
or do you send the code along with it as mdb.
What do you do if they want the code?

Thanks in advance

"Danny" <dannywork5@hotmail.com> wrote in
news:pIJac.180699$LX.26761606@news4.srv.hcvlny.cv. net:
[color=blue]
> If you created a database application for somebody, do you send the mde
> only or do you send the code along with it as mdb.
> What do you do if they want the code?[/color]

I might send an ade/mde to be distributed to the unwashed in an
organization, at the request of the organization, whose officers might
think this could minimize maintenance costs. But the main users always have
the mdb/adp.

I give them ALL the code. They can do whatever they want with it except
sell it or give it to some other entity.

Now I'm going to get zapped by Larry again but I have noted that developers
who are tight-assed about "THEIR" code, forms and other objects are, for
the most part, the least capable; that is they don't know that their work
is essentially worthless, and take great pains to TRY to protect nothing.

Notwithstanding ADE, MDE or ANYTHING else, a motivated capable developer
could create a close copy of any application in much less time than the
original developer took, probably a better application, and certainly a
more efficient one… that is if he doesn't vomit on his/her keyboard while
trying to effect that.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

I have delivered the mdb for a couple of applications to a small schood
(K-6) for asefveral years with no problems related to the code delivery. I
would have had more problems, probably, if I hadn't - at least they have a
good "backup" copy of the code if I should die or something.

From the standpoint of protecting against disasters, the queries and table
formats are not protected by the mde's and they can be the most dangerous
things to change in a complex application - especially the table-making
queries.

Dick