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

Monthly Access Rights

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

    Monthly Access Rights

    Hi All

    Is it possible to set my application up that every month on the first of the month it asks for a new password/access code to access the application, if so how would I go about doing this.

    My Goal: To Stop Users accessing the application that have not paid up thier monthly fees.

    Thanks in advance

    John

    #2
    RE: Monthly Access Rights

    Yes, it can be done. You would have to create your own registration routines to do it. I did it but it took many days to complete and I still have occasional problems with the verification routine not recognizing the registration number that was created so I have to check each one before giving it to anyone. Part of the issue, of course, is protecting it well enough to keep nosy users from figuring out how to circumvent it.

    By the way, my instruction sheets on just how to install the already existing functions is 1-1/2 pages long. I made the instructions immediately after installing it on my first (and so far only) app that uses it because I knew it would be difficult to figure it out the next time.

    There is a registration routine available on AlphaBay but I don't know if it provides the ability to create a monthly registration.

    Cal Locklin
    www.aimsdc.net

    Comment


      #3
      RE: Monthly Access Rights

      Hi John,

      You could make it more simple, no less effective.
      Why don't you programm 12 codes in the app in advance, and then email your customers the code after receipt of the payment ? With every new release, patch or update you can adjust or extend the list of pre-programmed codes.

      Of course it would be possible to crack it, but then again nothing is crack-proof. And if your customers would be that great crackers why would they buy a product from you instead of creating it themselves.
      You can always react on an attempt to crack by throwing the customer out. Most of the time this kind of behaviour does not stay unnoticed.

      Kind regards,

      Marcel

      Comment


        #4
        Re: Monthly Access Rights

        A new date question. re: repetitive invoices.

        In addition to normal invoicing, a medical supply Company has repetitive invoicing.
        Assume a client is renting a wheel chair and crutches, and has agreed to be invoiced every fourth month. If he started in Apr 2009, The next repeat invoice would be in July.
        A field in the header table "month" would be given a numeric value of 3.
        Different rental contracts have different billing cycles and are always at the beginning of a month. A current repeat-billing month may have anywhere from twenty to seventy-five repeat billings.

        In the header of this repeat billing set, is an invoice date, a billing cycle start date and ending cycle start date and a next due date. All billing cycle start dates are on the first day of a month. The next due date is also on the first of a month. All dates are in the header. The start and end billing cycles are printed on the invoice.

        The billing cycle for a 3 month April month billing would have the following dates:

        start cycle date 04/01/2009
        Ending cycle date 06/30/2009.
        The next due date would be 07/01/2009

        The invoice date usually precedes the cycle start date by a day or two and is globally entered on the actual invoice date.

        I need to call up around the last of each month all of the repeat invoices due on the first of the following month. For clarification On or about May 28 to May 31, I would like to have a button ( display next billing cycle ) call up all June 1 repeat invoices only.

        Subsequently, These invoices would be edited for content, new invoice numbers and new invoice dates assigned, then printed, then appended in 2 steps - First to a total repeat header table, and then to a total repeat items invoiced table.
        After printing and appending The final step would be to advance the cycle dates, which I have worked out. The header table also includes a month numeric code. the values are one of these [ 1, 2, 3 ,4 6 12 ].

        The billing cycle start date is a global adjustment based on the value in the month field. The ending cycle date field rule is "addmonths(cyclestartdate,month)-1" The next billing cycle date is the "ending cycle date +1".

        That initial "button" "display next billing cycle" seems to be my only problem. All other aspects I have worked out.

        I thought of creating twelve separate indexes for the first of each month, and twelve buttons invoking a particular monthly group of repetitive invoices, , but I am sure there is a simpler "one button" solution!!

        Help is always appreciated. I hope there is no limit to the number of times I can ask
        for help.

        John Linley

        Comment

        Working...
        X