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

opportunistic record locking

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

    opportunistic record locking

    does the Alpha WAS and/or the ClientServer model depend on opportunistic record locking?

    I have a big client where we are having data problems symptomatic of opportunistic record locking being turned on. IT agreed to turn it off. But they immediately began having problems with another, more important app, and turned it back on. I couldn't find out what kind of app it is.

    I'm not sure what we are going to do.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    #2
    Re: opportunistic record locking

    I haven't had to deal with it because it has never presented a problem. And Alpha's help has little to say about it:

    http://support.alphasoftware.com/alp...rd_Locking.htm

    I trust you know what you're talking about, but if you're not sure of a solution, howzabout describing the problem/symptom?
    -Steve
    sigpic

    Comment


      #3
      Re: opportunistic record locking

      http://msgboard.alphasoftware.com/al...ad.php?t=64791
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      [email protected]

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


        #4
        Re: opportunistic record locking

        OK, I've read and thought for a while, here are my thoughts:

        Thought #1:

        You said:
        the adb was apparently corrupted - ....
        I made a new database - that fixed it. I suspect opportunistic record locking as the cause.
        Record locking has everything to do with the data table, and nothing that I know of with the .adb, which is simply described as just another table (as you know) that keeps track of all the other tables in A5.

        I don't see how record locking in one table is going to cause a corruption of another. This is like saying I have a corruption problem with my customer.dbf and I'm sure it's caused by record-locking issues in my vendor.dbf. I just can't draw a cause-effect line here.

        Thought #2:
        I've implemented quite a few databases on various networks, and never had to instruct the network administrator to do something in particular with opportunistic record locking.

        Thought #3:
        You seem to be mixing the WAS into this, but I'm not sure why. Again, I don't see why the WAS' optimistic record locking has much to do with this at all.

        Thought #4:
        You say the record is gone, and even undeleting records doesn't bring it back. Are you able to identify the record number when it does exist? And then what's in the record-number entry after it disappears?

        Thought #5:
        Am I clear on this?: This is only happening to one table? While I can't explain how, why or what, my gut is that this problem is related to the integrity of that single table. One solution I'd try is to create the exact table structure from scratch. If the field rules aren't too involved, I'd create them all over again too -- otherwise just use some re-naming to get the .dd* stuff from old to new. And append all the data from old to new. In effect, do everything you can to use a new implementation of the problem table. If I'm wrong here about this, it's probably because I missed something in fully understanding the problem.
        -Steve
        sigpic

        Comment


          #5
          Re: opportunistic record locking

          thanks Steve

          the question about the WAS had to do with - given that many have reported
          they had to have IT turn off opportunistic record locking for regular Alpha
          on a LAN - wondering if the WAS depends on it being turned on. Thus a
          potential built-in problem.

          This the first time I've had a problem with oplock, also. And I can't
          actually prove that that is the issue. Just guessing, based on past posts.

          I agree with the idea that the table may have had problems. I was at that
          point grasping for straws. When as an experiment, I made a new adb, and
          added all the tables, the problem went away - the problem being that the
          table would not compact. The main problem, of course, is that the record is
          disappearing. Whether it is actually the result of a corrupted adb or table
          or opp locks remains to be seen.

          Prior to that all other attempts failed - like making a new table, copying
          records back and forth, etc.

          Its just that its perplexing that the record disappears.
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            Re: opportunistic record locking

            Your response got me wondering. Is it just one record all the time that's disappearing? I got the idea that it wasn't the same one all the time. If it's the same one, definite table corruption problem.
            -Steve
            sigpic

            Comment


              #7
              Re: opportunistic record locking

              I may have found the problem. I discovered that the table in question, "patients," was left open on the server - when Alpha wasn't running.

              When I discovered the problem, and since I couldn't reach IT, I renamed the folder on the server to 'mydatabse-save', and copied another copy of it from 'development' to the server.

              I made this change about 1:00 PM today, and have been watching it, remotely, since. So far so good. I'll find out tomorrow if the table 'patients' is still losing parent records. But the one symptom 'could not pack' has disappeared.

              I really appreciate your help with this!
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment

              Working...
              X