Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How to license an app I have written

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How to license an app I have written

    I am soon to be retiring and I am passing my Alpha-based desktop system to the buyer of my business. However, I would like to have my application advise the user when his license is due for renewal, i.e. at a specified date in the future. More importantly, what would be the best way to prevent the run-time's from opening the app after a certain date, i.e. if they don't renew their license with me?

    Many thanks, as ever

    Larry

    #2
    Desktop does not usually require an annual licence.
    Why is yours different Larry?

    I can supply you with some security measures to prevent Lift and Shift.


    ​​​​
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Apologies Ted, I didn't explain myself properly. When I leave my app with the new owner of the business, I want him to re-licence with me on an annual basis, for him to continue to use my app. I was planning to write a pop-up page that would trigger on a specific date and prevent him for continuing to use the app - but then I thought that all commercial developers probably have something similar built into their apps

      Comment


        #4
        Not sure they do.
        If you put a check in the startup, you can prevent tne app from running after a specified date.
        ​​​​Depends how long you plan to license it.
        Having a 10 year list of dates and activity keys might do it.
        You will need to hide the code in an AEX? file?
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        Apologies to anyone I haven't managed to upset yet.
        You are held in a queue and I will get to you soon.

        Comment


          #5
          Thinking more about this, I would probably do the following;

          Set Date for renewal (RD) as an encrypted one. (You could save it as a (licence key on public display if it is encrypted sufficiently)
          Count down from RD to Today and issue prompts as renewal approaches.
          If renewed, reissue encrypted date for the coming period and store it. You can add a KEY to prevent unauthorised decrypt.

          ? encrypt_string("01/01/2023")
          = "-4=-M$r*dB"

          ?decrypt_string("-4=-M$r*dB")
          = "01/01/2023"


          They may license for 2-5 years. Who knows!
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #6
            Thanks for the update Ted. I'll be back in the office tomorrow and Tuesday and will have a look then - and hopefully decide on a direction.

            Comment


              #7
              Hi Larry,
              What you propose is a simple concept with very complex enactment. Licensing one user to operate your system under a single registered license is a complex process. Having many users under a single license is more complex. I have developed several very robust modules to handle this, under various conditions, and exactly which conditions your needing will help to move forward.

              1. Is this a single user app with no user login?
              2. is this a single user app with a user login?
              2. Is this a multi-user app with no user login?
              3. Is this a multi-user app with a user login?
              4. What is the user login system if present?

              There is no question I can help you, it's just a matter of how much your app needs adjusting to accommodate your new need.


              Last edited by Mike Wilson; 10-30-2023, 12:17 AM.
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment


                #8
                Hi Mike,
                Thanks for your input and I think I see where you are going - simple when you know how :)

                Basically, my data is stored on a Windows server and currently four users login via Windows login and then access Alpha via Run Times on their individual PC's.

                I have a specified start-up form and also a Workspace password setup in Security settings, which asks for username and password.

                So on opening the Alpha workspace, a small PW form appears. Get it right and you arrive at the start-up form. Get it wrong and Alpha closes.

                I hope I have supplied the correct info.

                I guess what I would ideally like would be that on a certain date in the future, on successful login, instead of the usual start-up form appearing, a different form appeared first, advising the user that he had 14 days to renew his licence

                Comment


                  #9
                  Larry,

                  An add-in like Cal Locklin's AIMS Registration Routines​ might be helpfull to you.
                  Jo Hulsen
                  Dommel Valley Solutions
                  The Netherlands

                  Comment


                    #10
                    Mike
                    It doesn't seem like a login issue to me as it isn't a multi tenant app, just needs a complete block if the server accessibility date is not within the licence period.
                    I would put the check in the password/login form for the sake of simplicity.
                    Display a message and put a countdown in too.

                    If it was my choice, I would fix a price for a number of years and leave it there.
                    Paying a licence fee means expecting fixes and sorting out Msoft issues, so maybe Larry wants to support the app for a price?
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment

                    Working...
                    X