how to expire an access database that can be reactivated via password

How did you try to get this to work?

I'm not sure where you found it but looking at the code and making a few guesses it's meant to be code for a startup form.

That form would open when the database opened and the code would run.

There's a bit more than that involved, eg a table called 'TableExpire'.

Have you set the start form, table etc up?

By the way this code can easily be avoided by holding F5 down while the database opens, sorry.

>> ...that I want to have expire or lock after say 60 days....

Not an easy job, there are so many ways to defeat possible routes.

If I need to do this, I would be using Peter's product:

Keyed Access
http://www.peterssoftware.com/ka.htm

I use several of his excellent products in various apps.

mx

imnorie,

 hi, I put the code directly into my form via: Design view> View code. And then put it in Private Sub Form_Load()

I then created a Table called ExpireTable and a row called Expire

It threw up an error by highlighting the sentence starting CurrentDb.Execute

This was supposed to just timeout the database after 30 days I think.

AndyAinscow

Hi, I understand what you are saying, and I dont want to go too deep, as it is only a simple measure. I dont mind there being flaws where a clever guy would know how to bypass it. I was just hoping for something that would stop the average Joe. Do you think it will be too much to do?

DatabaseMX

Thats great looking software. It is $299 for it though. I am sure it is ideal but I was hoping for an alternative rather than paying for it, sounds like im being cheap, sorry, but I was hoping for a simple solution that probably is not simple. thats for the link though.

DatabaseMX
Oops..

Thats great looking software. It is $299 for it though. I am sure it is ideal, but I was hoping for an alternative rather than paying for it, sounds like im being cheap, sorry, but I was hoping for a simple solution that probably is not simple. THANKS for the link though.

I got the idea from this expert exchange article

http://www.experts-exchange.com/Microsoft/Development/MS_Access/Access_Architecture-Design/Q_23788525.html

You can take a look at these also:

Marcus Fisher (EE's harfang)
Need to supply purchasers with a software unlocking code
https://www.experts-exchange.com/questions/27074447/Access-Licensing-System-Recommendations.html?cid=1573&anchorAnswerId=35892087#a35892087


Add license key functionality to your source code similar to that used by Microsoft.
http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=25237&lngWId=1

http://www.ssware.com/cryptolicensing/cryptolicensing_ocx.htm
'Standard' version is less expensive that Peter's ... but ...?

mx

The very simplest way I can think of is the following - maybe it would be suitable.

Forget about any table / key to unlock the database.
Put a piece of code into the startup form as follows

Private Sub Form_Load()
If Now() >= CDate("#dd.mm.yy#") Then 
  Application.Quit
End If
End Sub

Select allOpen in new window

where dd.mm.yy is the date in the local format for dates (could be mm.dd.yy for instance) that you want it to expire upon- I think the CDate is the correct function to force it to be a date.

Now convert it to an mde - this prevents the end user being able to look at/modify code.


When they pay for the full version then you give them another copy but with the if...end if statement removed.

This is always a touchy subject.

*First* I would consult a lawyer.
Despite you best efforts and assumptions, you may not have satisfied all the legal requirements that you "own the database program"
In legal terms this has to be clearly spelled out in a legal document signed by both parties.
In other words, did you create a "Legally approved" EULA?
http://en.wikipedia.org/wiki/Software_license_agreement

Also note that by denying them access to the Application, you may be denying them access to "Their" data, ...another touchy subject, as it may be your program, but it is their data, and you cannot deny them access to it.

Again, this all has to based on a firm legal agreement,
...just you saying "I own the database program" may not stand up in court.

Again, consult a Lawyer first.


JeffCoachman

Yes ... I absolutely agree ... consult an attorney *first* ... it's not black and white.

mx

Yes you are right, I will have an agreement for it. Basically it will outline that the program is mine but the data is theirs. To which I can detach the tables and delete the forms etc

I will need to look a little deeper on thast subject and I thank you for raising it. But, any one know how to amend or fix my original code?

AndyAinscow

While I do like your answer, do you think my one can be tweaked, I would like it to check and see if a date exists and put it in but also later allow me to reset it again

Do you mean the code in the first post?

Did you get any error message when the line was highlighted?

I agree with Jeff, you need to be careful with this sort of thing.

Your employers could have some clause somewhere, eg contract of employment, that is meant fotr these sort of situations.

Might be something that says any work done on their equpiment is there, unless there has been a prior agreement, but in 'legalese'.

It's one thing to call something a 'demo version', which expires in N days, but this is a different situation.

Also, all of these schemes done in VBA code can, in one way or another ... pretty much be circumvented.  

Meanwhile ... try this:

Private Sub Form_Load()

    Dim myRecordedDate As Variant

    'lookup date
    myRecordedDate = Nz(DLookup("dtExpire", "ExpireTable"), "Empty")

    'insert expiry date if there is none
    If Nz(myRecordedDate, "") = "" Then
        CurrentDb.Execute "INSERT INTO ExpireTable (dtExpire) VALUES #" & DateAdd("d", 30, Date) & "#"
    End If

    If Date >= myRecordedDate Then
        'expired
        Application.Quit
    Else
        'let em in

    End If
End Sub

mx

DatabaseMX

thanks for that.
It does not seem to put a date in if it does not exist. If I put it in manually it is OK. One other thing. If I wish is to ask for a reset password is that simple to input.

Say something like:
 If Date >= myRecordedDate Then
' put in a popup box asking for password which is ExpireTable, dtPassword
,
this could be a simple word like letmein so that the database works afterwards 

imnorie

yes I got an error in my original:

in debug it highlighted the following line of code in yellow
runtime error 13
type mismatch


CurrentDb.Execute "INSERT INTO ExpireTable (dtExpire) VALUES " & Chr(34) & Format(Now(), "dd-mmm-yy") + 30 & Chr(34) & ";"

Remove +30 and change Now() to Now()+30.

That's assuming you want to add 30 days to the date, and then format it.

CurrentDb.Execute "INSERT INTO ExpireTable (dtExpire) VALUES " & Chr(34) & Format([b]Now()+30[/b], "dd-mmm-yy") & Chr(34) & ";" 

Select allOpen in new window

I was trying to bold the change but it didn't work.

Thinh I'll check how the forum deals with formatting.:)

"It does not seem to put a date in if it does not exist. I"

Standby ...

mx

Here you go:


Private Sub Form_Load()

    Dim myRecordedDate As Variant

    'lookup date
    myRecordedDate = DLookup("dtExpire", "ExpireTable")

    'insert expiry date if there is none
    If Nz(myRecordedDate, "") = "" Then
        CurrentDb.Execute "INSERT INTO ExpireTable (dtExpire) SELECT  #" & DateAdd("d", 30, Date) & "#", dbFailOnError
    End If

    If Date >= myRecordedDate Then
        'expired
        Application.Quit
    Else
        'let em in

    End If
End Sub

tucup,

Just a follow up:

<I own the database program>
Until they purchase it? ...or is this a "Licensing agreement".

Remember,  you can "Lease" the application to them or you can outright sell it to them.
There are no clear cut rules on this;
If you simply create the program for them, and it is fairly basic (Contacts, Simply Order system, ...etc)
You may just want to "sell" it to them (after all this 90 day stuff is cleared up)
Then you can simply get paid one chunk of money once and be done with it. (they can still contact you for support, if they like)
Remember, again, if this is a fairly basic database that *any other access developer can create*.

If, however, you are creating something highly specialized, or something that you may want to market to other clients, (and again, you are sure that *No other developer can create, or has created*) you may consider "Leasing" the app.

Many small clients may balk at your request to "Lease for a small fee", because they know they are tied to you for everything.
Some like the idea, because of the low initial cost.

But this opens up another can of worms about securing, distributing your app (...etc).
So again, these are things you should consider after the 90 day trial issue is resolved.

;-)

JeffCoachman

boag2000

Thanks for the advice.
Without going into to much detail.
I am not, as you probably guessed, a programmer. I researched, and scrounged as much as possible from the internet. Later adapting code for this, to the point where I could not reproduce it if I tried.

The company who use it, asked about a database but did not want to pay anything for this, even though senior staff all have Aston Martins etc. I told them I would design one that they could try but it was my programme. In fact, they refer to it as my program, I now have told them that as I maintain their servers etc, they could use it as part of the package ( so thereby securing my contract)
I now want to safeguard the code from being duplicated or used if they replace my services. I would of course make sure they get the tables of data. The database does do a lot of things, and I do add extras now and again.

The end..., long winded but now you guys know a little about why I wanted to somehow secure it.



DatabaseMX:

Thanks, that has solved the date issue, it puts it in perfectly.

Is it too complicated to add a password reset. So that if it reaches the finnal date, I get a popup asking for reset code  (simple password).

If you guys think it can be done but would take a litle time I am happy to do another request for a further credit:)

imnorie

Thanks for the update there, but I saw DatabaseMX`s answer and just cut n pasted which resolved the issue.

oops, spoke too soon.

DatabaseMX
your answer, though it puts a date in, it immediatly closes the database when next ran. I suspect it is not accounting for the "upto 30 days". it looks like it is just saying, ok its past or equal to today so close. I think it is not allowing a 30 period?



imnorie

your suggestion puts the following in RED under bug mode ( I am using ACCESS 2007)

CurrentDb.Execute "INSERT INTO ExpireTable (dtExpire) VALUES " & Chr(34) & Format(Now()+30, "dd-mmm-yy") & Chr(34) & ";"

hold on...
took space out in front of it, now in black...but still does not put a date in.
it seems happy with code, but does not do anything to ExpireTable. DatabaseMX`s does make the change, but expires the database on next run

@ "DatabaseMX
your answer, though it puts a date in, it immediatly closes the database when next ran."

I don't get that result.  If I clear the table, open the form ... it adds today's date. If I close the form, reopen - no problem - it opens.

So ... are you using Date or Now - which includes Time ?

mx