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

Disable opportunistic locking on either the client or on the server

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

  • Disable opportunistic locking on either the client or on the server

    I am trying to improve the speed of Alpha in a network enviroment, so I am revising my code and see that coding methods are very important factors in speed.
    Also I would like to try the tip posted by MS and By Ira in opportunistic locking.

    To disable opportunistic locking on the client, set the following registry value to 1:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled set to 1

    To disable opportunistic locking on the server, set the following registry value to 0:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\EnableOplocks set to 0

    I have the server as w2008 and stations as w7.
    Reading above code for the station with regedit, I have found that I am missing the \Parameters under MRXSmb.
    Do I create this key \Parameters and then enter the \OplocksDisabled ?
    It seems obvoius, I would just like to have a confirmation.

  • #2
    Re: Disable opportunistic locking on either the client or on the server

    Yes you would need to add the missing keys.

    Configuring opportunistic locking in Windows
    http://support.microsoft.com/kb/296264
    Andrew

    Comment


    • #3
      Re: Disable opportunistic locking on either the client or on the server

      Ok, Thanks.
      Will this change, by any chance will create index corruption or data loss?

      Comment


      • #4
        Re: Disable opportunistic locking on either the client or on the server

        You might check this thread. Cal Locklin created an .aex to do this this on either server or workstation. It is old, but I still use it in one app.

        Bill.

        Comment


        • #5
          Re: Disable opportunistic locking on either the client or on the server

          Originally posted by MikeData View Post
          Ok, Thanks.
          Will this change, by any chance will create index corruption or data loss?
          I cannot say for certain if disabling opportunistic locking will introduce index corruption issues or data loss.

          However according to this is article having opportunistic locking enabled can lead to to index corruption and data loss.
          http://www.dataaccess.com/whitepaper...adcaching.html
          Andrew

          Comment


          • #6
            Re: Disable opportunistic locking on either the client or on the server

            I have setup opportunistic locking according to instructions. 7 hours later the reports are from most users, no difference at all.
            2 users report a bit slower. I have tried the system remotely and I can not tell any difference.
            If the gain is in stability and data corruption prevention, will make me happier.
            The speed issue is not early, but as the day progresses.

            I will be going over the code in the areas of delay.

            Comment


            • #7
              Re: Disable opportunistic locking on either the client or on the server

              Mike,

              I have a client that was deviled by slow speed on network and I pulled my hair out over the years. They moved to a new building, got a new IT shop and new servers. The IT shop said the windows logon scripts for the network were inconsistent and a mess. With all new infrastructure Alpha is a dream. Good speed, no more random index issues, etc.

              I don't know how you get there from here, but something in the network or the way users connect to it may be an issue. One thing I do is copy a 100MB file with Windows Explorer between workstation and server to see if there is variability from one workstation to the next.

              Bill.

              Comment


              • #8
                Re: Disable opportunistic locking on either the client or on the server

                I have tested the system using lan_speed from www.totusoft.com and and get good consistant result in all work stations.
                Using the utility, found some staions were using cat 5 cables. once I changed them to cat 6, all are almost the same.
                Question
                said the windows logon scripts for the network were inconsistent and a mess
                Can you give more details in this area.

                So far revising the code, I found some problems with a call opening a table/form/browse. I am posting a sample in another thread.

                Comment


                • #9
                  Re: Disable opportunistic locking on either the client or on the server

                  Can you give more details in this area.
                  Unfortunately, no. I was not involved in that area and have not done it for myself before.

                  Bill.

                  Comment


                  • #10
                    Re: Disable opportunistic locking on either the client or on the server

                    Based on the other links presented here I decided to revise my aex file. It will now show a message then abort if someone tries to run it on anything later than XP - which means pretty much everyone today.

                    FWIW, there seems to have been a lot of confusion about Opportunistic Locking and network speed. To the best of my knowledge there is no relationship - stopping Opportunistic Locking may have helped some index issues but it's not intended to have any effect on speed. And today I'm not even sure those old issues weren't more of a network setup/equipment issue than anything else.

                    Comment

                    Working...
                    X