Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6576 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

Hi,

I have a question about creating a DEMO version of an application with a date expiration.

I have read several postings, which state that someone has created a DEMO of their application by using a “Date” expiration. However, I have never seen a posting as to how they accomplished the expiration…I have made many attempts to create a “Date” expiration but have yet to accomplish it.

I have successfully created a DEMO of my application by using a limited number of entries before the DEMO locks up. I would really like for the user to be able to enter all the records they want, so that the can do a full test drive of the application and have it expire after 15 or so days.

Does anyone know where to point me to learn more about creating a DEMO which will expire after a certain number of days after the initial install?

Thank you for your time and assistance.

Jim

Edited by Guest
Posted (edited)

Hi Jim

Here is roughly how I did it.

Create a field 'date first used' in my main file.

This field is empty on distribution.

In your startup script the first thing that you need to check is if this is the first time that the solution has been run. This can be done by checking if your 'first used' field is empty.

Pseudocode:

If firstused field is empty,

set firstused to Get(currentdate)

Show appropriate welcome message.

Go to main menu

endif

If not Isempty(firstused)

If (Get(currentdate)-'firstused' field < 16

Go to main menu

else

Show message (your time has run out. contact.....)

endif

endif

This is nothing more than the skeleton of my startup checks but should give you one idea of how to approach it.

You will need to make sure that the user cannot gain access to this script or any layout that holds the field first used. I also include checks to see if the user has reset the clock on their pc and see if the user is logging on for the second time that day so as not to bother them with duplicate messages.

I actually give my users 30 days but after the initial explanation that this is the allowed time I do not bother them again until they only have 15 days left and then I remind them of how many days they have left each time they log on for the first time in any one day.

The complexity of the checks that you do is entirely up to you and what you feel is appropriate.

Please understand that what I have posted here is by no means what one would call secure but is an attempt to answer your question as to how it might be accomplished

HTH

Phil

Edited by Guest
Posted

Thank you very much for the starting point...I have tried to create such an animal, but apparently I was off in the wrong direction.

With your info I should now get on the right track and create what I need.

Thanks again for your time.

Jim

This topic is 6576 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.