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

Disable opportunistic locking with backend db's?

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

  • Disable opportunistic locking with backend db's?

    Hi, all.

    Is the problem of table corruption with opportunistic locking only with native Alpha databases, or does it also exist with backend SQL databases like MySQL? The documentation doesn't give a definite answer.
    Jim

  • #2
    Re: Disable opportunistic locking with backend db's?

    My read of the white paper on Opportunistic Locking (Dennis Piccioni May 14, 2002) would leave me to believe that applies to ALL database systems, not just Alpha. Disable it to be "better safe, than sorry" as your grandmother often told you????
    Bruce Cavenaile

    Comment


    • #3
      Re: Disable opportunistic locking with backend db's?

      Hi, Bruce!

      Thanks for your response. The reason I ask is that the procedure for disabling opportunistic locking contains a scary warning about the possibility of ruining the operating system, so I want to avoid doing that if I can.

      I've located Mr. Piccioni's white paper. It looks like just what I need.

      Thanks again.
      Jim

      Comment


      • #4
        Re: Disable opportunistic locking with backend db's?

        It looks scary but really not that scary. Just do a backup of your registry before you make any changes. Before you enter or change anything sit & study for a little bit so you do not make a error. Once you get done you will realize it was easy to do.

        Comment


        • #5
          Re: Disable opportunistic locking with backend db's?

          Jim

          Don't be too concerned about the dire warnings from the Evil Empire. Heed the preceding warning about backing up and then go ahead as directed in that white paper.

          I found that some of the registry keys didn't exist and I had to create a couple but it isn't a huge deal.
          Bruce Cavenaile

          Comment


          • #6
            Re: Disable opportunistic locking with backend db's?

            Thanks for the advice and encouragement, my friends.

            I've never edited the registry before, so I was more than a little wary. You've removed my hesitancy.
            Jim

            Comment


            • #7
              Re: Disable opportunistic locking with backend db's?

              In this thread on the v6 message board I offered to send my OpLocksOff.aex file to anyone interested. I still will if you still have need of it. (The neat thing is that it can be added to an app that is given to a customer and the customer's computer can be updated more or less automatically - it does give them the option just in case they don't want to do it.)

              Edit: I just restored the file to my website. You can download it from the link mentioned in the other thread. (Capitalization of the thread path is critical on that site.) PLEASE READ THE INFO I PRESENTED IN THAT THREAD BEFORE USING IT. If you have additional questions, post them here - and feel free to contact me directly if I don't reply right away.
              Last edited by CALocklin; 04-12-2007, 11:13 PM.

              Comment


              • #8
                Re: Disable opportunistic locking with backend db's?

                Hi, Cal!

                I was hoping you'd join in. (I know you've written a lot about this topic.)

                I've downloaded the aex file and hopefully will get to try it out soon. I'll keep you posted on this thread.

                On the other thread you mentioned, there was a comment that disabling opportunistic locking may degrade the performance of client-server applications. For the sake of argument, this mean that disabling is not required if I'm using a SQL database backend? (The Microsoft documents give this impression.)

                It's very kind of you to offer your addin for free. Thank you very much.

                Jim
                Jim

                Comment


                • #9
                  Re: Disable opportunistic locking with backend db's?

                  Originally posted by jmatienza View Post
                  ... there was a comment that disabling opportunistic locking may degrade the performance of client-server applications. For the sake of argument, this mean that disabling is not required if I'm using a SQL database backend? (The Microsoft documents give this impression.)...
                  That's my understanding. Although I suspect the degradation is minimal, I really have nothing to base that on except suspicions. If both SQL and .dbf files are in use, I'd opt for disabling the opportunistic locking. I'd trade a small hit on SQL performance for a larger hit in .dbf reliability.

                  Comment


                  • #10
                    Re: Disable opportunistic locking with backend db's?

                    Cal,
                    Thanks for the OpLocksOff.aex file I downloaded and will test it out and report back. I share your concern for MS keeps changing registry names from OS to OS making you need to create the "shotgun" approach. Which leads me to the obvious question. How does one know Oppurtunistic Locking is on or off on any given server or pc?
                    Thanks
                    Peter
                    See in Las Vegas

                    Comment


                    • #11
                      Re: Disable opportunistic locking with backend db's?

                      Originally posted by pk9 View Post
                      Cal,
                      How does one know Oppurtunistic Locking is on or off on any given server or pc?
                      Thanks
                      Peter
                      See in Las Vegas
                      I believe by not having any problems (bad way to find out) or looking at the registry

                      Comment


                      • #12
                        Re: Disable opportunistic locking with backend db's?

                        Turbojack,
                        Looking at the registry does not definitely state it is on or off. A review of MS KB shows varied names. I assume one could place a registry entry that is not interpeted as anything and just bypassed by the OS. That is why there should be a way to test.
                        Peter

                        Comment


                        • #13
                          Re: Disable opportunistic locking with backend db's?

                          The problem with opportunistic locking does not affect MySQL or any other SQL client-server database. It only affects databases in which all the workstations have equal access to tables, e.g., Access, Foxpro, Alpha Five, Data Access.Goldmine, ACT, etc. In MySQL or other client-server databases all the database requests go through a single central server database engine, so the whole question of opportunistic locking becomes moot.

                          - Peter

                          Comment


                          • #14
                            Thanks!!!

                            Peter, thank you for an answer that was concise, definite, and supremely enlightening. Your patients are fortunate to have a doctor who communicates like that.

                            Thanks to all who posted. I've gotten what I came for, plus a free addin from Cal.

                            What a nice forum this is!
                            Jim

                            Comment


                            • #15
                              Re: Disable opportunistic locking with backend db's?

                              Originally posted by pk9 View Post
                              How does one know Oppurtunistic Locking is on or off on any given server or pc?
                              I executed Cal's OpLocksOff() function in the interactive window. A dialog box popped up informing me that the system is not optimized for dbf indexes (i.e., that opportunistic locking is enabled). So I made the selection to optimize (disable opportunistic locking).

                              When I tried OpLocksOff() again immediately afterward, the dialog box no longer popped up. I guess that means that opportunistic locking has been turned off.

                              Now, is there a way I can take a look at that dialog box again?

                              Cal, are you there?
                              Jim

                              Comment

                              Working...
                              X