RE: Urgent: Securing My Access from Piracy
From: Martin J (anonmous_at_nospam.com)
Date: 02/07/05
- Next message: Joan Wild: "Re: Calling Joan Wild"
- Previous message: Joan Wild: "Re: No permission to use file.mdb problem"
- In reply to: Baghzaad: "RE: Urgent: Securing My Access from Piracy"
- Next in thread: Paul Overway: "Re: Urgent: Securing My Access from Piracy"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Feb 2005 09:51:10 -0800
As long as you understand this option is easily broken... you would make a
function on startup Run it from autexec macro that would ask for a key based
on date (a simple algorithm is think of a 6 letter password and add the
digits of the date to the letter of the password a+2=c) if accepted have a
yes/no field in your control file or somewhere saying his key is good
otherwise exit. If he figures out where the yes/no field is or figures out
your password your security is broken. Also he can still copy the front end
now and use it if he has a full version of access installed on another
machine or try to install it on another machine using the same password and
changing the system date to the date originally installed.(Make it 8 digits
and include hour might make it slightly harder I wouldn't do minute because
it changes too frequently) As I said before its a matter of value.
HTH
Martin J
"Baghzaad" wrote:
> Hi Martin,
>
> Thanks for replying. See my Application is entirely made in access with
> forms, reports, etc. Now when I give it to tham I will make an MDE. Now they
> can easily give the same MDE to anybody in his field even try to sell it and
> I am in a fix as I cant find any solution to avoid that. Now yr first option
> will be good enough ("ask for a key on installation maybe dependent on date
> or whatever") but frankly I dont know how to implement it. I would be highly
> obliged if you could explain me in detail or give me a code for it. Pls reply
> as soon as possible.
>
> Thanks.
>
> "Martin J" wrote:
>
> > There is no 100% secure way of making sure it cannot be used on another
> > machine. The real question is how much is your program worth to you? and how
> > much time your willing to spend to protect it. Plus how hard is it for them
> > in time to break your protection? if your selling your program for $500 and
> > it takes 20+ hours of there time it probably wasn't worth it for them.
> > However if it was $5000 its a different story. Here are a few strategies to
> > stop them from coping. 1) ask for a key on installation maybe dependent on
> > date or whatever. 2) Write an encrypted license file of some sort on paid
> > machines that can be checked on start up with the computer serial # or
> > something like it. 3) if your database is split make it hard after
> > installation for them to change the path to there backend data. 4) more
> > advanced would be requiring a new license file ever month. What ever you
> > decide to do remember that they have to be able to reinstall it if there
> > computer breaks down and be able to back it up. An MDE just makes sure code
> > is never visible.
> >
> > HTH
> > Martin J
> >
> > "Baghzaad" wrote:
> >
> > > I have a MS Access Application (.mdb). I want to make my application secure
> > > from getting copied or used on any other computer than the one it is
> > > installed for. I have also made a MDE for my client but just realized that he
> > > could use it on any other machine or make a copy of it. How can I avoid my
> > > Application which is entirely created in access from duplication or from
> > > piracy.
> > >
> > > Thanks
- Next message: Joan Wild: "Re: Calling Joan Wild"
- Previous message: Joan Wild: "Re: No permission to use file.mdb problem"
- In reply to: Baghzaad: "RE: Urgent: Securing My Access from Piracy"
- Next in thread: Paul Overway: "Re: Urgent: Securing My Access from Piracy"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
