Hi,

I would like to add a time limit to my application. So that after a certain time period the application will no longer be able to open. I can then issue the user a new license key or a new version of the software. Something of that sort. I know security measures can be defeated, but I am trying not to make it as simple to defeat as rolling back the windows clock.

Purpose: This Application is for internal company use only. In the event a user leaves the Company and takes the software with them to another Company, I would like to know the software will eventually expire.

I have created an Access Application using:

• Windows 7
• Access 2010 (64 bit)

I will be deploying this application with Runtime 2010 (32 Bit) and Runtime 2010 (64 Bit)

I have been racking my brain over here for days :/

Any help would be GREATLY APPRECIATED

Thanks in advance,
Dave

Does it need to be a standalone application, or would the users always be connected to the company network. I haven't done this myself, but if they were on the network, you could just check for something on your company's server to allow it to open.

Just a thought.

The application will be mainly for Field Use with laptops not connected to the network.

Not sure if you looked through this topic yet, but it may be something along the lines you're looking for.

http://www.UtterAccess.com/forum/Database-...ys-t564179.html

I don't have much experience in the security aspects either, but am intrigued by your question. One other idea might be that the user must activate it while connected to the network upon first use. After that, you could base the usage period on the laptop clock, and if the clock's date ever goes back by more than 1-2 hours (account for daylight saving time), you could make the application inoperable. I'm sure there's probably a workaround to this as well, but haven't yet thought that far ahead.

This post has been edited by darnellk: Apr 29 2012, 08:37 PM

I gave that one a try without luck. I would even be open to purchasing 3rd party software but I have yet to find one that works with my version of access or with any actual examples in the newer access accdb format.

Hi Dave

I've created several new database properties and use a pseudo random number authorisation code,

The expected authorisation code is stored in a db property and if this is entered into the db by a user then the expiry date is calculated and entered into a second database property.

To prevent the user circumventing the expiry data by winding the system clock back, a third property is used which stores the date the database was last opened. If the system date is earlier than the date the db was last opened then the code can detect this and prevent the db being opened. An informed Access developer can work around this but it does make it more complex then just winding the system clock back.

hth

Wow that sounds great. Are you able to send me the code/instructions?

Thanks,
Dave

Hi Dave

Sorry for the delay, been busy! I've also had to extract the code and tidy it up a bit (IMG:style_emoticons/default/wary.gif)
So although it has been tested, and used! it will need checking out further.

Note that the code creates and uses properties in the db back End, you will need to have at least one linked table to the BE, and to specify this table in the constant 'strLnkTbl'.

hth

Bernie,

I appreciate your help. This works well. (IMG:style_emoticons/default/smile.gif)

I have the following questions:

1. How can I modify this to expire after say 3 Months?

2. testing purposes trying to roll the windows clock back how can I go about setting the app to expire in a day or so?

Thanks,
Dave

Hi Dave



If you add the following sub to the module, then set dtExpire to the date you want (in format mm/dd/yyyy) and run the sub, it will set the expiry to the date you want.



hmm, now that is more tricky as the authorisation code will have to vary on a month to month basis, you will have to replace each occurence of DateAdd("yyyy", 1, Date) and each occurence of Year(Date) + 1
Let me give this some thought!

hth

PS: I left out a line of code in the function CheckAuthorisation()
Could you add the line dbs.Properties("Lastdate") = Date Immediately before the line CheckAuthorisation = True

Hi Dave

I've changed the db to specify a constant (intMntExp) as the number of months expiry.
then changed the calculation for the expiry date dtExpire from
dtExpire = DateAdd("yyyy", 1, Date) 'Current authorisation expired set new authorisation 12 months from current date
To
dtExpire = DateAdd("m", intMnthExp, Date) 'Set expiry date (intMnthExp months from today's date)

I've also changed the Check code calculation to call NextAutCode, which will return the authorisation code based on the 1st day of the month (this means that an authorisation code will ony be valid for a month!)

if you want to be able to set varying periods for the expiry, e.g. 3 months and 12 months, then you will need to make intMntExp a variable and be able to pass the expiry period for the database as (e.g.) part of the authorisation code.

hth

NB: I've modified the attached db but have NOT tested it any further!

Wow I am very impressed!! I can't thank you enough.

This is exactly what I had in mind. The testing procedure worked great as well.

(IMG:style_emoticons/default/thumbup.gif)

(IMG:style_emoticons/default/yw.gif)
Good luck with your project.