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

After making some updates with all users off except for the main one, no users can get back in.

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

  • After making some updates with all users off except for the main one, no users can get back in.

    Using v11 runtime in a shadow db win7 stations and server 2012.
    In the middle of the day there is a task that will update few tables.
    So I have the users go off and proceed to do the updates from only one user.
    After completion of task, no user can get back to the system.
    The problem: as the users logs in and enters username and pw, the program exits after the pw. No error message or anything.
    I have to shutdown the server. After rebooting all is back to normal.

    Any advise?

  • #2
    Re: After making some updates with all users off except for the main one, no users can get back in.

    as the users logs in and enters username and pw
    Examine how this is handled.
    There can be only one.

    Comment


    • #3
      Re: After making some updates with all users off except for the main one, no users can get back in.

      Mike, do you see the same result if a user tries to log in twice in a row, with the second attempt failing as you describe ?

      Comment


      • #4
        Re: After making some updates with all users off except for the main one, no users can get back in.

        Thanks Stan, It is normal process, It works all the times.
        What is there to look for?
        My feeling is somehow a table is left open, but It appears that all operations in the task are completed.

        Comment


        • #5
          Re: After making some updates with all users off except for the main one, no users can get back in.

          Thanks Tom, Yes, several attempts have been made. Same result.
          This problem is quite hard, there are so many factors.
          I guess I have to try to do the complete task and eliminate one step at a time and see which one will trigger the lockout.
          There are 17 steps in this task.

          Comment


          • #6
            Re: After making some updates with all users off except for the main one, no users can get back in.

            No one here has direct knowledge of the process, coding, etc which you use to implement security and have the users login nor what happens after they attempt to login to verify the password. Is it a custom process or Alpha's? You didn't specify.
            There can be only one.

            Comment


            • #7
              Re: After making some updates with all users off except for the main one, no users can get back in.

              I am using the security system by Alpha. Create users, give them password and form to start.
              This problem is not consistent. So it hard to diagnose.
              In general, if Alpha exits after the user enters the password; should I assume that the user table is unavailable to login with no error message?
              Could a primary table be left open and not ready to use?
              How can I make sure upon exit, make sure that all tables are closed and the user data is also closed as well?
              In other words close everything. It seems that 'exit' is not doing it
              Could it be something in the server 12 software leaving some locks open?

              Comment


              • #8
                Re: After making some updates with all users off except for the main one, no users can get back in.

                Create users, give them password and form to start.
                What form?
                should I assume that the user table is unavailable to login with no error message?
                what user table and where is it located?
                What updates are you doing in the middle of the day?
                Dave Mason
                dave@aldadesktop.com
                Skype is dave.mason46

                Comment


                • #9
                  Re: After making some updates with all users off except for the main one, no users can get back in.

                  Mike, the table.in_use method() could be used to step through the applicable tables, and then identify which are open somewhere on the network.

                  Comment

                  Working...
                  X