how to use add 12 month expiry date to access prg

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • neelsfer
    Contributor
    • Oct 2010
    • 547

    how to use add 12 month expiry date to access prg

    Can one add an expiry date/code of say 12 months to an access application, after which the user must add a new code to continue to use application?
  • MMcCarthy
    Recognized Expert MVP
    • Aug 2006
    • 14387

    #2
    You'll have to work out the logic in a lot more detail first. For instance ...
    • Is the code just going to change every 12 months?
    • Will all users will have to enter new code at the same time?
    • Will each users 12 months start at a different time?
    • Will each user have a different code unique to them?


    These are all the questions you will need to sort out before you even think about programming something like this.

    Comment

    • neelsfer
      Contributor
      • Oct 2010
      • 547

      #3
      it would be nice if you can start the program with a code and 12 months later the client have to renew it with a new code again, similar to the activelock application. Activelock is a VB feature with a keygen. Can one build such an application into Access 2007?

      Comment

      • MMcCarthy
        Recognized Expert MVP
        • Aug 2006
        • 14387

        #4
        So what we are talking about is some kind of licencing. Not my area of expertise but I'll see if I can find someone with a better handle on this.

        Mary

        Comment

        • neelsfer
          Contributor
          • Oct 2010
          • 547

          #5
          thx mary. Its a race timing application i am building. Dont want everybody to just copy,paste and use it

          Comment

          • NeoPa
            Recognized Expert Moderator MVP
            • Oct 2006
            • 32661

            #6
            I guess it would need to be released as an executable.

            You'd need a table which stored the date, encrypted, that the project would work until, and a procedure for taking in and verifying a code, as well as saving a new encrypted date when the code was found to be ok.

            PS. You'd also need a procedure to run each time the database is opened that checks that the encrypted date had not been overtaken by the current date of course.

            Comment

            Working...