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

Preventing users from logging in during backup

  • Filter
  • Time
  • Show
Clear All
new posts

  • Preventing users from logging in during backup

    I have managed to use a modified version of the excellent info given in the article by Dr. Peter Wayne in Shut Down Your Alpha Five Network to make use of Alpha's inbuilt security.

    This successfully logs out all users except those belonging to a group called Super_Admin (one person). My problem is that users could still attempt to log back in while a backup is being carried out.

    My thought was that I could add a logical field into the sys_control table called prevent_login. I could then call a script from the autoexec.bat file that checks if this is true and the user does not belong the the Super_Admin group. If so, a message box is displayed and the database closed.

    My concern is that I do not know what order Alpha executes the scripts. I do not want the script to execute before the login screen or I will effectively log the Super_Admin out of the database as well, and there will be no way to get back in.

    At present the main form (opened first by all users) is linked to a dummy table that is not used when making a backup, so I think the act of logging in does not access any of the tables used by the backup.

    Any help would be much appreciated. :)
    If computers are so clever how come someone as dumb as me has to tell them what to do?

  • #2
    Re: Preventing users from logging in during backup

    Hi Paul,

    I have used Dr. Wayne's scripts for a long time for my situation. The same article as you used.

    If a user attempts to log in, they will be kicked out. So if all the users are either timed out or loged out and then attempt to log in, you have no problem.

    I altered the article a little bit to work with the build in Alpha security.

    Do a little testing on your part. Just make a copy the data base and put it in a test folder, and play with your settings, to make sure you have it right.



    • #3
      Re: Preventing users from logging in during backup

      Thanks Ed.

      Once again I am trying to make things more complicated than they really are ;)

      My problem is that I work on a standalone machine, and don't have the opportunity to test something like this before updating the version on the client's server - I therefor always look for the worst case scenario in the belief that "anything that can go wrong, will go wrong"
      If computers are so clever how come someone as dumb as me has to tell them what to do?


      • #4
        Re: Preventing users from logging in during backup

        I know the feeling. (Must be a TV show ..Fear Factor..).

        You want it to be right.

        Best thing lots of backups. I had a fortune cookie one time "Expect the best, but be prepare for the worst".



        • #5
          Re: Preventing users from logging in during backup

          I found that if users tried to log back in they would receive the message about system shutting down in 10 mins (time set in sys_config table), but would still be able to log in.

          Also, any new user could log in, and would be shown the same message.

          I added a logical field to the sys_config table called "prevent_logon".

          I created a group called "Super_Admin" and placed one user in it.

          The form below is only accessible to the "Super_Admin" group......

          I placed an "on change" event on the multi-state button that sets the time to shutdown - if the "Run" button is seleted "prevent_logon" is set to False, otherwise it is set to True.

          I now run a script from the autoxec file that contains the following code:
          DIM SHARED prevent_log AS L
          prevent_log = .F.
          t ="sys_control",FILE_RO_SHARED)
          prevent_log = t.PREVENT_LOGON
          I then check if the user is in the "Super_Admin:" group. If they are, I exit the script and they are logged in, regardless of the value of the "prevent_log" variable. If not, and value of the "prevent_log" variable is True, Alpha5 closes.

          There are probably more elegant ways of doing this, but my client is happy because it works for them.
          If computers are so clever how come someone as dumb as me has to tell them what to do?


          • #6
            Re: Preventing users from logging in during backup

            Copy :)

            Tnx For Sharing Paul
            It Helps A Lot
            "Knowledge without application is useless."