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



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

NIST Password recommondations

  • Filter
  • Time
  • Show
Clear All
new posts

    NIST Password recommondations

    Since I worked through this for a client I thought I would share. We've all gotten used to having to create "complex" passwords for websites. The new NIST guidelines say "additional research shows that requiring new passwords to include a certain amount of complexity can actually make them less secure. And that’s why NIST has also removed all password-complexity requirements from their guidelines."

    Read here for the full guideline:

    Their guideline makes perfect sense. Like, forcing the user to change their password often, makes it less secure because we just add a "$" to the existing password, or change "...28" to "...29", etc.

    It also calls for letting the poor user actually see the password they are typing in stating, that if they cannot see the password, they tend to create shorter, less secure passwords.

    The slightly more difficult one to implement is to compare the password they entered in real-time against a database of known unsafe, compromised, or too-common passwords.

    Also, they recommend not using those stupid questions like the name of your first pet or the name of the street you grew up on.

    Also, no SMS for 2-Factor Authentication.

    Come to our Webinar: If any of this is important to you, we will probably talk about it at our next IADN webinar. Please click here and plan to join us. All of your software-developer friends will be there.

    Steve Wood
    See my profile on IADN

    Thank you for passing this along Steve. We have been so ingrained in thought about passwords for so long that some of the new recommendations almost seem counter-intuitive now .. but if you really think about it, do make a lot of sense!
    Alpha Anywhere v12. Build 8540-5670 IIS v10.0 on Windows Server 2019 Std in Hyper-V


      Really interesting read. Thanks for sharing.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Independent Developer & Consultant

      My Alpha Components​​​


        This is somewhat "old" news with the NIST document being over 2 years old, and yet many (most?) are not aware of it. Thanks for sharing it here Steve.

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation


          And why do humans have to prove to computers that they are not a robot?


            I tend to offer a "hint" which is only known to the user.
            Password = 1972Disney!
            Hint = Micky and Goofy!

            Tends to get remembered as there is an association, holiday in Disney Land.
            See our Hybrid Option here;

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


              Soon we all are using FIDO auth (and then everything else is considered as a bad practice as usual). So basically a pin is enough.


                I have that already, Ken.
                Not hassle free.
                Think biometric situations where gloves are reqiired. A PIN should actually be enough if you can link it to the device DNA, which, as we all know, Google and MS already do.
                A bit like the "Remember me" feature that doesn't work ( but could).
                All my CCs are pin operated and pegged to the card, so that is the same as device DNA really.
                See our Hybrid Option here;

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