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

Who Is Logged In

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

    Who Is Logged In

    Is there a way to return a list of all users currently logged in to an application?
    The context security methods allow calls to see the current logged in user but not all logged in users as far as I can tell.
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    #2
    You can get a list from SQL Server.

    Comment


      #3
      I sort of do that already, I have a login activity table which displays all login activity .. Login Failed, Login Succeeded, Logged Out, Password Change Succeeded, Password Change Failed, etc.
      It requires parsing through and trying to figure out who is logged in and who is logged out.

      Login Activity.jpg

      In speaking with Terry at Alpha, in order to accurately track logged in users, it would require a "last request time" and "last access" log that needs to be updated in a SQL table. You would surmise from the last activity whether the user
      is logged off if there were no activity within the session lifetime. Given the amount of work to add such a feature to Alpha, I told them not to pursue it further on my behalf.

      The logout method is highly dependent on whether the user actually use the logout or not, so it's not particularly accurate.
      I was hoping for a simple function to return just a list of users currently logged in. I may try to simplify my login activity table query and use a query based on time and login/logout requests.
      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

      Comment


        #4
        What would the SQL Query be for returning a list where the login date = today's date?

        This doesn't work:
        WHERE LogType = 'LogIn' AND LogTimeStamp = GETDATE()

        Nor does this:
        WHERE LogType = 'LogIn' AND LogTimeStamp = CAST ( GETDATE() AS DATETIME )
        Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

        Comment


          #5
          Getdate() and logtimestamp() are both date and time fields. You need to set them both to date using cast, or try th following:

          WHERE LogType = 'LogIn' AND LogTimeStamp between cast(getdate() as date) and GETDATE()

          Comment


            #6
            Thanks Larry, that works !
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #7
              In regards to what Terry from Alpha suggested, another similar suggestion is to have the main container of the web app (the tabbedUI in my case) periodically do an Ajax callback in the OnTimer event.
              In the callback, stamp some field that you keep in your own user table to indicate the date/time of last contact from that user. Something as simple as:


              UPDATE dbo.UsrLogin
              SET ulLastAliveDtTm = GETDATE()
              WHERE ulUsrLogin_GUID = :pUserGuid


              I keep a SQL script handy that lets me see a list of users whose workstations contacted the server within a specified time frame:

              declare @gNow as datetime = GETDATE();
              declare @minutesThr as integer = 10;
              select ulUsrID, ulIsSignedOn, ulSignOnDate, ulLastAliveDtTm, DATEDIFF(minute,ulLastAliveDtTm, @gNow) as LastContactMM
              from UsrLogin where DATEDIFF(minute,ulLastAliveDtTm, @gNow) < @minutesThr OR DATEDIFF(minute,ulSignOnDate, @gNow) < @minutesThr;

              Last edited by RichCPT; 05-08-2021, 05:04 PM.

              Comment

              Working...
              X