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

Table locked by another session or user

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

    Table locked by another session or user

    I'm going to keep this initial post high-level in case this is a known problem.

    We are running a multiuser environment with a master database located on a networked drive. Each user has a runtime Alpha operating on a shadow database saved to their local workstation. Several users have the full version running off the master database.

    Every once in a while we hit a problem with one of our most used tables, "order detail." Some sets linked to the table will be unaccessible. Form or report based off these sets cannot be edited or opened. At times Alpha will report that the set cannot be found.



    The table itself can be opened directly. A script can parse through each record and check order_detail.is_record_locked() without finding a single .t. value.

    The solution is always the same: use smbstatus to discover who has the table open, then have them exit the appropriate forms. Once the last person has stopped accessing the file, normal operation can resume.

    It's a bizarre problem, and I have had little luck troubleshooting thus far. If anyone has a suggestion, I would be glad to hear it.

    Thanks.
    Last edited by abackstrom; 02-09-2007, 03:55 PM.
    Adam Backstrom <[email protected]>

    #2
    Re: Table locked by another session or user

    It's not telling you that the table is locked by another user.It's saying it's in use by another user.
    My guess is that thet the order detail index is becoming corrupted.When you try to access the set Alpha's auto child index tag creation is trying to kick in and can't because the file is opened somewhere else.I have no experience with what you are using for an operating system, but with windows turning off opportunistic locking seems to reduce index problems.

    Comment


      #3
      Re: Table locked by another session or user

      Originally posted by JohnZaleski View Post
      Alpha's auto child index tag creation is trying to kick in
      Could you elaborate on this a little, or point me to some documentation? What sort of events would trigger this index tag creation? I'm not familiar with it at all.

      We've had oplocks disabled in our Samba server for some time now, which is unfortunate because I was hoping for an easy fix. =)

      We disabled one of our more problematic indexes this morning. This index (along with several set linking fields) was built by concatenating two numeric values that had been converted to strings. Here's hoping our order detail table is problem-free tomorrow morning.
      Adam Backstrom <[email protected]>

      Comment


        #4
        Re: Table locked by another session or user

        To reproduce what I am talking about, create a very simple set with a one to many link to a child table. When you do thhis you will see that Alpha has created an index automatically for you. If you erase this index and then, with the child table not open anywhere else,open the default form for the set , you will see that Alpha will have created the index again for you. After you erase the index, and purposely keep an instance of that table open., Try to open the set again, I think you will see the same error that you have seen on your present system.Because Alpha can't get exclusive access to the child table, it can't add the necessary index tag. Without an appropriate index on a child table, Alpha cannot opent a set.

        Comment


          #5
          Re: Table locked by another session or user

          Thank you, John. I think you hit the nail on the head. This goes a long way to explaining some of the problems we've been experiencing.

          This is one of the times when I wish the Alpha error messages were more descriptive... I might suggest an alternative to, "table in use:"



          ;)
          Adam Backstrom <[email protected]>

          Comment

          Working...
          X