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

How to Prevent a user logging in twice on a 5 user LAN?

  • Filter
  • Time
  • Show
Clear All
new posts

  • How to Prevent a user logging in twice on a 5 user LAN?

    A user can log in as many times in a LAN, what is the code in basic to prevent a user from logging in twice or more. Cashiers passwords are sometimes secretly stolen by keylogger softwares.A cashier is complaining why he/she sold so much more than the total in his/her drawer. only to find out that another user logged in using his/her log in name on another workstation.

  • #2
    Re: How to Prevent a user logging in twice on a 5 user LAN?

    Sounds like you need to create a "logged in" table to your startup sequence.

    When the opening form is loaded code could run to check the "logged in" table to see if the current user is already active. If not, a record is entered to that table. And then, when the user logs out that record is deleted. On the other hand if the user is found in the logged in table, the app could be shut down after explaining to the user what's happened. This kind of system cries out for a password protected override to be run by the administrator only so that mishaps in the logged in table can be administratively cleared.

    Not sure if others have tackled this before. Have you searched the code archive forum?

    Have you checked the articles list at www.learn

    These are wonderful resources. You should get familiar with them.

    -- tom


    • #3
      Re: How to Prevent a user logging in twice on a 5 user LAN?

      Thanks Tom, sounds your suggestion is the way to handle it, how can I do that? Searching www.learn ........


      • #4
        Re: How to Prevent a user logging in twice on a 5 user LAN?


        Well you could hire someone to build it for you.

        Or, you could take pencil and paper and write down the sequence of steps that must be followed to achieve your goal. This would be the steps you'd want Alpha to do for you. Small steps please. Alpha can only do one thing at a time.

        Then, write the code to convert your narrative into xbasic so Alpha can run the sequence for you. This is done by converting each step in the narrative into its xbasic equivalent.

        If I were doing this I'd develop the plan, and write the code, to run from a button. Then after its working correctly I'd move it to run on an event that fires whenever the startup form is run.

        If you'd like to learn how to do this, try writing the narrative plan, without using any code, and post it here. We'll help you fine tune it. Once the plan is complete you can begin coding, and we can help you when you get stuck.


        • #5
          Re: How to Prevent a user logging in twice on a 5 user LAN?

          Firstly - it's a given that the design does not allow duplicate log-ins - no matter how it is done, and it is not difficult, simply check!
          Secondly - many many months back we (and I gave at your request, codes and techniques) wrote of users' invoice header table unique to each. Locked. You never did this?
          One basic reason is no second event of this table could possibly occur, anywhere, by anyone, anyhow.
          You're dealing with cash sales - a fiduciary issue with anti-theft precautions being a primary objective.
          This aside from security discussions with user log-in.
          I am astonished that the client still allows you to continue, none of mine would have.
          Last edited by Ray in Capetown; 03-03-2013, 03:18 AM.


          • #6
            Re: How to Prevent a user logging in twice on a 5 user LAN?

            Another simple thing I do is with a date/time field recording each new sale header. An audit easily discloses whether a cashier is using the system weakness to their advantage.
            Keyloggers stealing passwords???? in a closed network - hardly likely