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

Force shadows to close

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

  • Force shadows to close

    Is there a way to either force shadow connections to close down or at least to detect if there are any shadows connected?

  • #2
    Re: Force shadows to close

    User_Count as N = A5_REGISTRATION_LICENSE_INUSE( MUF_or_RMUF_File as C )

    Not strictly shadowed count, just the runtime user count. Depends on how you have things set up.
    There can be only one.

    Comment


    • #3
      Re: Force shadows to close

      Does not seem to work with the unlimited runtime. Both the MUF and RMUF files remain at zero bytes and the A5_REGISTRATION_LICENSE_INUSE( MUF_or_RMUF_File as C ) shows 0 users even with multiple computers using the app. It does work if using the developer.

      It could be that I do not use runtime throttling so it is not counting anything. I use AIMs to restrict the number of computers that can open the app at the same time as that can be changed just with the license number I give them.

      I will try setting the runtime throttling to 1000 and then see if it counts the number of computers using the app. If not then I will contact Cal and see if there is a way to read the number of computers from the st6muf.apq file.

      Edit:
      Nope, applying runtime throttling still results in a zero user count.
      Last edited by preston2; 04-15-2016, 02:55 PM.

      Comment


      • #4
        Re: Force shadows to close

        Rmuf and muf should know when users are in there regardless of others.

        I use this to get number of users on the system in my ae. It works on dev or RT

        Code:
        cpath = a5.Get_Path()
        cmast = a5.GET_MASTER_PATh()
        regusers = a5_registration_license_inuse(cmast+"\sales.muf")
        runtimeusers = a5_registration_license_inuse(cmast+"\sales.rmuf")
        totalusers = runtimeusers+regusers
        Dave Mason
        dave@aldadesktop.com
        Skype is dave.mason46

        Comment


        • #5
          Re: Force shadows to close

          Does not work Dave. Totalusers shows 0 with one master using runtime and one shadow using runtime. I even put a .control file in each computers runtime directory.

          It counts if using the developer but not the runtime.

          Comment


          • #6
            Re: Force shadows to close

            Ok, I got it to count using a corrected version of what Dave posted. I also found that part of the problem was that license number change from the test app Cal put out.

            That said and while this may work for what I need now, I do not like it and may just come up with my own way of detecting a shadow.

            Thanks all.

            Comment


            • #7
              Re: Force shadows to close

              Preston,

              The onTimer event in forms can be used to periodically check a table field value. If that field contains a specific value the onTimer event can close the form and exit Alpha. This will have the effect of closing Alpha on all workstations. I think a code example is present in code archive forum, or maybe Dr. Wayne's LearnAlpha website. In practice the administrator would set the value that gets polled, so workstations would then close. Later, the administrator changes the value to something else so the users' workstations can resume normal operation.

              Comment


              • #8
                Re: Force shadows to close

                Tom,

                I have looked at one posted by Craig Schumacker but it uses toseconds() and shuts down the shadows at a certain time of the day.

                I have yet to find any documentation on the onTimer event that runs when a form is open.

                Comment


                • #9
                  Re: Force shadows to close

                  Do you only want to shut down shadowed connections? Or all instances?
                  -Steve
                  sigpic

                  Comment


                  • #10
                    Re: Force shadows to close

                    Originally posted by Steve Workings View Post
                    Do you only want to shut down shadowed connections? Or all instances?
                    Just the shadows.

                    Comment


                    • #11
                      Re: Force shadows to close

                      Brief discussion of onTimer event here. Scroll down page to list of Form Events.


                      Example here.

                      Comment


                      • #12
                        Re: Force shadows to close

                        Update.

                        I contacted Cal Locklin and he believes like I do that the A5_REGISTRATION_LICENSE_INUSE() lacks a lot and is limited in the info you can get from it.
                        As a result I got a set of functions from Cal that allow for much more information and easy of use telling who is connected. I cannot show the code of the functions as Cal has asked that if anyone is interested to please contact him.

                        I modified the functions I got from Cal a bit to provide the information I wanted to see. I will be creating some additional functions to use with the ones I got from Cal and should be able to end up doing just what I want.

                        For now, here is a screen shot of the results I get using the functions from Cal.
                        whos_on.png

                        Comment


                        • #13
                          Re: Force shadows to close

                          Video of what I have so far.

                          I have resolved some of the Form closing that I talk about in the video, but not all yet.

                          The message board seems to not allow Full Screen mode on the video so you may wan to watch it on Youtube directly.


                          Comment

                          Working...
                          X