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

User Login

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

    User Login

    Has anyone created a user login with a password for the start up form? My thinking was a user/password table where the user would input the name password to variable fields on the start up form that would be checked for user name and password in the user/password table. Or any other method for user logins.

    Thanks
    Sean Tucker

    #2
    RE: User Login

    ya I did some time ago....
    I had a login screen that made a log of date and time the user went into the system.
    it used a lookup that had to match...
    if you would like I will look for it...

    Comment


      #3
      RE: User Login

      That would be great, that's exactly my intended purpose.

      Sean Tucker

      Comment


        #4
        RE: User Login

        Sean,

        You can get as complicated as you want with this idea. I use password protection on nearly every app using a user table. All apps have an autoexec script which sets a number of global variables. One variable that is set is a variable called code, which is a character variable. (could be logical if only a single access level is needed) All apps also start at a mainmenu form. On the Onactivate event for the mainmenu, I check if a value for the global code variable is set. If it isn't, I run a script that has the following line (and others)

        pass_name = upper(ui_get_password("Password","Enter Password","","*"))
        '/// set to upper case for consistency

        I have a table with fields for user name, user password, and access allowed. The script checks if the password exists, and if it does, sets the code variable to the value of the access allowed field. The access code I use has many characters, up to 24, which are just + or -. I use this so I can use a ui_get_check() box to set the access levels. Whenever the user tries to open a form I use the following to check if access is allowed. Access is allowed if the code in the specified position is +, otherwise a message comes up indicated access is denied.

        if substr(code,2,1)="+"
        if is_object("Inventory") then
        Inventory.show()
        Inventory.activate()
        else
        :Form.view("Inventory")
        end if
        ui_msg_box("Access Denied","Sorry, you do not have access to this form.",UI_INFORMATION_SYMBOL)
        end if

        Whever a user logs off, the code is reset to a blank value. You could just use a logical T or F for the code, which would be much simpler.

        Actually, I usually do a lot more. I also sometimes use a log file that saves the user name, and the logon date and time. Forms have to be developed to add, modify, and delete users. I use an encryption scheme to encrypt the passwords and access levels to prevent somewhat smart users from opening the user table in another viewer and modifying thier access. I also allow each user to reset their own password. The original development to cover all needed activities took some time, but now is essentially a boilerplate operation.

        Jerry

        Comment


          #5
          RE: User Login

          Thanks! I'll give it a go.

          Sean Tucker

          Comment


            #6
            RE: User Login

            We use a fairly intricate logon/password system, I have attached our apd and security table fo you to view. When the user signs in, variables are established, checked against a security table, then, if OK, the security level is established. This level follows the user throughout the system, and is stamped on any information that they modify.

            Tom

            Comment

            Working...
            X