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

Record locked by another session or user

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

    Record locked by another session or user

    I am using a single user version of A5v4.03

    I have a tabbed form with 11 tabs which is quite comprehensive and using many tables.

    On one record only for a client I am unable to enter or alter any information as I am always getting the above error message.

    The problem does not seem to exist on any other client's records.

    It would appear the problem lies with the parent table as the embedded browse tables are OK. However, if I go into the parent table in browse mode it lets me change the offending client record!

    I have tried re-indexing and compacting the database and closing it down and restarting it but still it is telling me the record is in use and therefore locked.

    Is there anyone out there who can advise me how to resolve this problem

    Jim Scott

    #2
    RE: Record locked by another session or user

    Most likely the problem is with your form, not with the tables.
    You can test this by seeing what happens if you try to
    change the record in the default form for the set. If that works,
    then you know the problem is with your form, which, from
    your description, sounds very complex. Most developers have found that
    it just isn't worth it to make very complex forms--it's too hard
    to figure out where there are problems. It's a lot more efficient and
    a lot simpler to curb one's enthusiasm and keep data entry limited to
    small sets and relatively simple forms.

    Comment


      #3
      RE: Record locked by another session or user

      Thanks for coming back to me so soon - it is much appreciated.

      You are right it is quite a complex form and when I go to create a default form it responds "Default form full. Not all fields will be displayed�

      That is a great shame as I and many others who have seen the application have commented most favourably on it.

      What I do find odd is that the other clients forms seem to be OK and it is a pity that just this one is causing a problem.

      Jim

      Comment


        #4
        RE: Record locked by another session or user

        Jim,

        I have never had that message about the default form. I have had it using the quick report feature of the report generator.

        But,you're not dead yet. As Dr. Wayne said, you need to verify the source of the problem.

        For starters, can you edit the offending record in the default form, even if it omits some fields? If so, edit the default form and add the missing fields. Then what?

        I would also look closely at the data because there is something odd about the form failing only for a particular record. Pay specific attention to the value of the linking key(s).

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Record locked by another session or user

          Hi there Bill, its the menace again from Scotland

          I have done as you suggested and can confirm the same client "fails" in the default Form.

          I suppose one of the options open to me is to delete all reference to that Client but that opens up another problem in that each client has a generated sequenced ID No and everything is hanging off that both within the system and within the organisation i.e. accounting system, filing etc

          Jim

          Comment


            #6
            RE: Record locked by another session or user

            Ureka

            Thanks folks for your help

            I have soved the problem - but I am left pondering why

            What I did was create a new form using the same set and the problem was still there. I then created a form only using the parent form and all was OK I then decided the fault must lie with the Set and went into it and set all the integrity rules to None I then checked the tabbed form and all was working for the offending client!

            What I don't understand is why if the fault lay with the set then why did it work for 99.999 per cent of the cases and only fail on the one?

            However I will persevere with my investigations and gradually change the set to cascade changes one at a time until I find the offending one.

            Thanks again all and I hope this matter being on the Message Board may prove useful to others.

            Jim

            Comment


              #7
              RE: Record locked by another session or user

              Jim,

              Is there anything unusual in any of the linking key fields used throughout the set for the problematic record? I'm wondering if you've include errant keystrokes, or punctuation symbols? In the past I've had trouble with slash marks, semi-colons and asterisks, for example.

              -- tom

              Comment


                #8
                RE: Record locked by another session or user

                Thanks Tom

                The short answer is I don't yet know but I will burrow down into it and find out.

                In the main all the records are linked using the Client Generated Number but there are a couple of others and I will investigate further

                Thanks for your help and advice

                Jim

                Comment


                  #9
                  RE: Record locked by another session or user

                  Do you have a circular reference in the set? That is, does
                  one table appear more than once in the set?

                  Comment


                    #10
                    RE: Record locked by another session or user

                    Well well well - thanks for raising the point

                    In fact I had one table linked to another child table while it was also linked at the bottom to the parent table.

                    Thanks very much - all in the garden seems to be rosey again

                    Very many thanks to all who have come to my rescue

                    Jim Scott

                    Comment

                    Working...
                    X