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

Multiple logins by same user

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

  • Multiple logins by same user

    Does anybody know how to prevent the same user from being logged in at the same time from different computers?

    Thank you.

    Jeff

  • #2
    Re: Multiple logins by same user

    http://www.learnalpha.com/ShutDownNe...ownNetwork.htm

    Using some of the concepts discussed in the above link you should be able to accomplish your goals.
    Andrew

    Comment


    • #3
      Re: Multiple logins by same user

      Originally posted by aschone View Post
      http://www.learnalpha.com/ShutDownNe...ownNetwork.htm

      Using some of the concepts discussed in the above link you should be able to accomplish your goals.
      Yes, that definitely suggests concepts I can work with to create a test of whether a user is already logged in and prevent further login. Thank you for this.

      Jeff

      Comment


      • #4
        Re: Multiple logins by same user

        Originally posted by Jeff Fried View Post
        Does anybody know how to prevent the same user from being logged in at the same time from different computers?

        Thank you.

        Jeff
        Are you talking about 1) network logon, 2) A5 security system logon or 3) your own home grown logon system? Answer that and maybe I or someone else could point you in a better direction.

        Raymond Lyons

        Comment


        • #5
          Re: Multiple logins by same user

          Originally posted by Raymond Lyons View Post
          Are you talking about 1) network logon, 2) A5 security system logon or 3) your own home grown logon system? Answer that and maybe I or someone else could point you in a better direction.

          Raymond Lyons
          #2

          Comment


          • #6
            Re: Multiple logins by same user

            Jeff,

            The link Andrew pointed you to is a good one for what it is trying to accomplish but I think what you want is significantly different.

            Using A5's security system, in the autoexec you could use USER_NAME() to get the user who just logged on. It would be nice if A5 had a built-in way of determining who is logged onto but to my knowledge there is no built-in way to do that. In that case, you probably want to create and maintain a table of who is currently logged on, adding the user when he/she logs on and deleting them when they log off (actually it would probably be better to use a logical field in a table so that you are not constantly adding and deleting records). Years ago I created an app with a similar table and users were automatically added and removed from it when the user was added or removed from A5's security system (it can be done). Anyway, when someone logs on you could use USER_NAME() in the autoexec to get the name and then see (in the aforementioned table) whether that user is already logged on, and if they are then don't let them proceed into your application.

            The one problem with such schemes is that they are not foolproof in that a crash (for example) would result in the table indicating a user is logged on when they are not (i.e., their computer crashed and the logical field indicates they are still logged on). Thus an administrator (AND at least one in some other group as the Admin could be the one that crashed) needs to be able to clear the crash problem in the table so the user can get back in.

            Or maybe someone else will have a better idea. Good luck.

            Raymond Lyons

            Comment


            • #7
              Re: Multiple logins by same user

              Originally posted by Raymond Lyons View Post
              Jeff,

              The link Andrew pointed you to is a good one for what it is trying to accomplish but I think what you want is significantly different.

              Using A5's security system, in the autoexec you could use USER_NAME() to get the user who just logged on. It would be nice if A5 had a built-in way of determining who is logged onto but to my knowledge there is no built-in way to do that. In that case, you probably want to create and maintain a table of who is currently logged on, adding the user when he/she logs on and deleting them when they log off (actually it would probably be better to use a logical field in a table so that you are not constantly adding and deleting records). Years ago I created an app with a similar table and users were automatically added and removed from it when the user was added or removed from A5's security system (it can be done). Anyway, when someone logs on you could use USER_NAME() in the autoexec to get the name and then see (in the aforementioned table) whether that user is already logged on, and if they are then don't let them proceed into your application.

              The one problem with such schemes is that they are not foolproof in that a crash (for example) would result in the table indicating a user is logged on when they are not (i.e., their computer crashed and the logical field indicates they are still logged on). Thus an administrator (AND at least one in some other group as the Admin could be the one that crashed) needs to be able to clear the crash problem in the table so the user can get back in.

              Or maybe someone else will have a better idea. Good luck.

              Raymond Lyons
              Ray,

              I've been thinking about which way to go on this. I hadn't thought about the delete approach, which certainly has merit. I already capture each login and logout in a file with date and time, user, and whether it was a login or logout. This captures an ongoing history of logging activity, and I could use it to determine the last record there for the user who logs in. If a login is attempted when the last record is a login, then it fails with a message saying to see the administrator. The administrator could then have access to the user log and simply delete the last login record. This would certainly work.

              Another approach I was considering is having a one-record file for each user. That record is updated with the login or logout for each of these events. The reason for this approach is to simplify the posting to the specific user's data file, though the bottom line is the same. This is a situation where there are local network users and external Citrix users. The Citrix server is a shared version, so the overhead required to keep track of individual directories for each user is a bit tedious but workable. Therefore, each user login would have code referencing the path to the user's login/out file. I may use this approach even though it's a bit redundant since I will continue to gather the in and out history. Then, when the administrator at this client needs to undo a crash-type situation, all I need to do is have the administrator select who the "shut out" user is and it will simply post a logout to that user's logging file.

              I agree that it would be nice if a mechanism was built in to Alpha to easily control for multiple logins by the same user, but in the absence of that, there are several ways to make it happen.

              Thanks for the follow-up.

              Jeff

              Comment

              Working...
              X