Does anyone have any advice about how to protect your
application?  I'm talking about everything.  I know to distribute
it as a .mde file so that there is no code involved, but can you
think of anything else?  I'm thinking I might want to add a password
to the backend database, but if so, how do I allow the front end
access without the user having to type in passwords all the time?

Additionally, if anyone has any hints on how to copyright the software
in a bullettproof manner, I would appreciate it.

I will shortly be giving a demo version of my software to a large firm,
and I expect them to try and steal it from me.  I want to make sure I
am completely covered before I let them see it.

Please reply by email as well as in the discussion group.  My email
address

Thanks a lot.

Douglas Hansknecht

For a demo version :
 Build in a date limit, if now () > #date# then end
 or build in a few checks on the number or records and place a limit on it.
 This way a life test is possible but can't be used for real.
 Spread the number and type of checks so there is no single point to patch.

 All simple software protection can be cracked.
 For more protection you need hardware (added or existing) to check where
the program is running.

Douglas Hansknecht heeft geschreven in bericht

Personally, I don't do business with people I don't trust.  But then, I can
afford to do that, I appreciate that not everbody can.

For what it's worth...

    - Rebecca.

only don't use #date#
use Dateserial instead, because some local settings can use dd/mm/yy
instead of mm/dd/yy, and this will cause an error

I tried to send you the answer yesterday. I thing it didn't  work. So, I
retry.

Protect your code and objects (make an MDE file). Then apply the Access
security to your application (and data).
Go to Tools, Security...
Create UserGroups (one will be yours - the one that can see the objects,
another will be for your users, limited to execution.
You can set the password for your application.
Then, you apply a trick with a date, after which the user won't be able to
start the application. Well, it is possible to back the system date, so:
- put the expiration date in a table
(the structure of the table can be something as: Expiration_date;
Grace_limit, Actual_Counter)
- set the number of execution after date is expired  (field: Grace_limit);
if date is really expired, display the message to buy the complete version,
i.e. to contact you; on open of your splash screen (form), find the counter
(Actual_Counter) in a table and increase it by one; if Actual_Counter is
smaller then Grace_limit, update Actual_Counter field and let the user use
the application.If grace limit is over, on Open event of your first form,
just put the condition that makes: QUIT.

Michel Jasic

Sorry Doug, it's just not gonna happen.  Copyright protection is nice
and all, but all they have to do is let you take them to court and then
drag it out until you're out of money to fight them.

Obviously, you can put a password or date-based bomb in so your software
won't work after a certain point, but it's certainly not bulletproof.

If you already know they're gonna steal it, don't give it to them.  I
know, I know, it's a bad position to be in.  Good luck!

--
Erika Yoxall
Hammer Data Systems
Access FAQ  http://www.hammerdata.com/Newsgrp

Hi Doug

The legal profession interprets this as though:... two pieces of software
are different even if they are identical in every way except the colours of
the screens. ie someone could copy your software functionally and make a
trivial change and claim it to be a different product.

The legal people have rather more ability in recognising that 2 pieces of
written text are identical and that could apply to two pieces of written
code. However, I would not bank on this, and since you are distributing an
mde you probably will not be worrying about that.

As the person who wrote the software you are the legal owner of it and are
entitled to all the rights associated with it. In practice, however, it is
very expensive to assert this and you will almost certainly not want to try.

In one response to your posting Michel gave lots of useful practical advice.
I do many of these things and they are good things to do.

1)  If you are concerned that they may purchase one licence and then install
it on many PC's you could consider shipping software with a dongle (I have
never actually done this) or use a registration ID that changes every time
it is used and requires them to call you for the ID (I have successfully
used an algorithm that takes the date and time of the installation and does
some "arithmetic" to these) or use your imagination. Or sell them a site
licence and stop worrying about it.

2) If you think that they will make modifications to the software after they
get it then sell them a licence to do so and stop worrying about it.

3) If they have a number of sites or if they have associated companies then
customise every copy that you sell to them with the name and address of the
location "hard wired" into the software. It is extra  work but it looks as
though you really care :-)

4) If  you think that they will use your demo as a resource and then not
bother buying the software then send them a video. You could send them a
lotus ScreenCam demo on CD or Video (you may even be able to make them pay
for this). Better still, do the demonstration in front of them, that shows
how important they are and gives you another chance to judge if you want the
trade.

5) If you believe you can sell the product to others and you think that they
may steal your ideas and do the same then tell them to get lost.

That is all I can think of right now off the top of my head. I do not get to
newsgroups very often so let me know how you get on.

Good Luck