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

Looking for advice for dual validating actions

  • Filter
  • Time
  • Show
Clear All
new posts

  • Looking for advice for dual validating actions

    I am needing to create a way to dual validate by two different users for each process in a narcotics tracking module we are including in our next software version. I will highlight the processes and am looking for advice, ideas or suggestions.

    When new vials of a narcotic is ordered, it needs to be approved/validated by two different personnel approved to do so. When it is delivered, it needs to be validated again by two different personnel, and when the narcotic is either administered, expired or submitted to the local DEA personnel to be destroyed it again needs to be validated by two personnel.

    My thought is to include a new field in the security tables called "PIN" which will be a 4-20 character password to serve as an electronic signature password. I realize there is no perfect way for this and passwords/PIN numbers CAN be discovered, but if the person enters their name from a dropdown and enters the correct PIN number then that is about as close as i we can get to confirming the users identity. Now that is for one person for a particular action, i still need to have another person do the same thing, select their name and enter their PIN for that action.
    So when the delivery arrives, i would use my PIN and who ever else is approved to validate the delivery would enter their PIN. So now i need to somehow document that the delivery process has been dual validated. I am trying to wrap my mind around how to accomplish this, but would like to get input from others who may have already crossed this bridge.

    I was thinking, probably wrong, but i would include 1 logical field and 2 char fields for each process that needs dual validation. the two char fields would be for the users PIN, or their name, which would be validated before saving and once there has been two correct validations, the logical field would be set to .t. so it would show that validation is completed.
    Epigate Software, LLC.

    [email protected]

  • #2
    Re: Looking for advice for dual validating actions

    Wel maybe I am not understanding it.
    But suppose you have a status field.
    Delivered approved 1
    Delivered approved 2
    Administered approved 1
    Administered approved 2

    hth pieter


    • #3
      Re: Looking for advice for dual validating actions

      Create the aproveal transaction in a seperate Database and table use Pieter field examples
      Delivered approved 1
      Delivered approved 2
      Administered approved 1
      Administered approved 2

      your data fields

      transaction ID
      userid (encrypted)
      password (encrypted)
      PIN char(4) (encrypted)

      Further security optimalisation to store the reference userid,password plus pin in a seperate DB + table then from the DEA transaction record reference to a encrypted key link as FK in your admin(employee) that pickups the reference autorisation key from the external database. Check the FK key for tamper before transaction if there is no valid key authentification then lock the fk link key.
      Also force change of pin after 60 days and keep audit trail for changes. Next the DEA transaction table must have One Time Insert Transaction Level.

      This is just a example for howto if you need more help let me know
      Last edited by bea2701; 06-09-2012, 05:50 AM.