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
Devcon 2020 Goes Virtual! LEARN MORE >

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

PROBLEM: "RECORD LOCKED BY ANOTHER SESSION OR

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    PROBLEM: "RECORD LOCKED BY ANOTHER SESSION OR

    I want to open another thread for the same problem I reported earlier, which remains unresolved. The issue I am now faced with is unless I am able to get this problem solved, my application is unusable. So the 150 or so hours I will have spent on the application will be totally wasted effort and I will never again be able to put A5 forward as solid commercial solution.
    The problem I have is I get an error whenever I try to update a record in table. The error is "Record locked by another session or user".
    I have tried everything possible to get rid of this problem including packing the database and re-indexing all tables. I have tried re-booting, facing Mecca and even holding my breath in a wind change. Nothing works.
    I originally thought the problem had been caused by my PC locking up (Windows XP). But this is not the case as several earlier backups of my database display exactly the same problem.
    The problem is easily reproduced in the attached TESTIT database. It's compressed in Zip format.
    I have pruned my TESTIT database down to the essentials needed to demonstrate the problem: 5 tables, 1 set and 1 form. There is an enclosed screen dump in JPEG format within the ZIP archive. This demonstrates the error message that is obtained whenever a record is updated via the form "Comp event round results".
    To demonstrate the problem, extract the enclosed TESTIT Zip archive to any convenient folder and then open the "WGA competitions" database. Open the form "Comp event round results" and then try to update any of the fields in the imbedded browse at the bottom of the form. You will get the error "Record locked by another session or user".
    Please can someone with A5v5 expertise tell me what I have to do to solve this problem.
    Tags: None
    #2
    RE: PROBLEM:

    your set works fine with the included tables, but the set referes to "venue", team a, team b (not in zip file). Remove those tables from your set, and you should eliminate the record lock error. Then, add them back (if needed) and see which one, and the link that causes the problem. I created a new set from scratch, using the tables included and was then able to change values, and edit field rules. So....the problem is with venue, team a, or team b, or all of them.

    Comment

      #3
      RE: PROBLEM:

      edit your set
      turn off referential integrity between the parent table and "team_a" and the parent table and "team_b".

      one-one linked tables are really "lookup" tables and it does not make sense typically to cascade a change in the parent key to the child table.

      take alphasports for example. in the invoice.set
      invoice_header is linked one-one to customer.

      if invoice_header has customer_id of (say) 000001, that might link to a customer called "sinclair"

      if i then changed the customer_id in invoice_header to 000002, i would typically intend to link that invoice to AMOTHER customer. I WOULD NOT intend to change the customer id for "sinclair" in the customer table from "000001" to "000002"

      Comment

        #4
        RE: PROBLEM:

        edit your set
        turn off referential integrity between the parent table and "team_a" and the parent table and "team_b".

        one-one linked tables are really "lookup" tables and it does not make sense typically to cascade a change in the parent key to the child table.

        take alphasports for example. in the invoice.set
        invoice_header is linked one-one to customer.

        if invoice_header has customer_id of (say) 000001, that might link to a customer called "sinclair"

        if i then changed the customer_id in invoice_header to 000002, i would typically intend to link that invoice to AMOTHER customer. I WOULD NOT intend to change the customer id for "sinclair" in the customer table from "000001" to "000002"

        Comment

          #5
          RE: PROBLEM:

          Eureka!! Yes, it worked. I changed the referential integrity for the links in the set for TeamA, TeamB and Venue to "prevent changes" and it cured the problem! Terrific, many thanks.
          I think the problem has been in trying to re-use sets where possible so that I don't end up with a multitide of similar set definitions. Changing the set definitions or links for one form may conflict with the set's use by another. Something to look out for, particularly in my case when the "record locked" message didn't give me enough of a clue as to the true cause. Anyway, thanks for the help guys. I can get on with it now.

          Comment

            #6
            RE: PROBLEM:

            Thanks, John. Yes, all fixed now - see below. The labels TeamA, TeamB and Venue are all aliases for the same table, club.dbf.

            Comment

            Previous template Next
            Working...
            X