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

List of current users logged on

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

    List of current users logged on

    Is there a way to get a list of all the users that are logged onto my database? There are occasions when I need all users logged off, but someone is still logged in, and I'd like to be able to know who they are so I can contact them. Thanks

    #2
    Re: List of current users logged on

    Ray, I don't think there's a built in function that will do this for you. Here are two ideas for you.

    a) when each user signs in you could enter a record to a separate table with field values that identify the user. When the user closes Alpha five a script could be run to find and delete the previous entry for that user in that separate table. Your administrator would then have only to check the table to see who's logged in at any point in time.

    b) Check the Code Archive Forum and also the articles at www.learn alpha.com for articles that show you how to shut down Alpha Five on unattended workstations. If I recall correctly they use scripts that are started when the startup form loads, perhaps using the onTimer event of the main form, assuming it remains open throughout the database session. This script periodically checks a table on the server automatically. If that table contains a specific field value then the script alerts the user, and then shuts down the application, otherwise it goes back to sleep until the next timer event... This same approach could be used to send messages to the logged in users, from the administrators' workstation. You'd have the message text saved in a table by the administrator. The onTimer event would display a dialog or message box that included the administrator's text, or do nothing if there is no text.
    Last edited by Tom Cone Jr; 01-17-2009, 08:12 AM.

    Comment


      #3
      Re: List of current users logged on

      Hi Ray,

      Alpha security has an option to create a logfile of who has logged on and when. Unfortunately it does not automatically record when they logged off. This would in fact be a nice feature. However, this would not be too difficult to write some code to perform that task.

      With regard to clearing every one off the network, as Tom has recommended, there are several options for this.
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


        #4
        Re: List of current users logged on

        Thanks. I'll give these a try.

        Comment


          #5
          Re: List of current users logged on

          I recently wrote a series of routines and code sections that can be used to force a shutdown. This includes shutting down forms opened in "dialog" mode and shutting down modal xdialogs. (I believe modeless xdialogs close when the app closes - at least I know it didn't require anything special for them.) These routines DO require editing each xdialog which means that they cannot be used with xdialogs that are still in an action script. It also requires that some xbasic code be added to form events and the autoexec script.

          These routines were needed to cover the situation where someone (1) left the app open, (2) left the workstation, AND (3) the developer was trying to log in remotely after hours to make changes. This was not a situation where the developer could just call someone and ask them to shut down. The routines also work even if someone is still working at the workstation.

          They also give a warning on each workstation before shutting the users down. The time of shutdown and warning intervals are set by the user as part of the setup for the shutdown. The warning messages even change from a blue background to a yellow background as it gets closer to shutdown time and, finally, to a red background at 1 minute before shutdown - if that isn't enough to tell the users to quit and log off, I don't know what is.

          I'm not sure I want to give all this work away for free - and my customer probably wouldn't be happy if I charged him for it (I did) then gave it away for free on the message board - but, if you're interested, send me an e-mail and we can discuss it. (Click my name on this thread and select Send an E-mail.)

          Disclaimer:
          The routines use the same basic concept that Tom described but they go further than what's listed in the LearnAlpha forum and it took days to get them all working right. In other words, it can be done by anyone with the desire/willingness to take the time to figure it out and then test it until it's working right.
          Last edited by CALocklin; 01-18-2009, 12:59 AM.

          Comment


            #6
            Re: List of current users logged on

            Originally posted by CALocklin View Post
            ...These routines were needed to cover the situation where someone (1) left the app open, (2) left the workstation, AND (3) the developer was trying to log in remotely after hours to make changes....
            If it is after hours and you can be reasonably sure no one is actually doing anything (or doing anything critical), and if you have admin rights to the server, it is easy, at least on server 2003, to identify and shut down all the open A5 files. I have done this a number of times over the last few years, made my changes, and have yet run into any problems.

            That said, it would be nice either to have Cal's methods (better than anything I would do) or better yet this is something Alpha should build in as a standard feature. I suspect the reason they haven't is .... well, I guess I won't give an opinion on that!

            Ray Lyons

            Comment

            Working...
            X