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

config.sys and file locks

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

    config.sys and file locks

    Does anyone know in detail the effects of each sections or parts of the config.sys file have on Alpha Four. I have one main file sharing server and 15 constant users and up to 10 more that hit the server rarely. If more than a 2 people use hit the same database even using different sets they get a file lock error. Any suggestions.

    This is two questions i guess.

    info
    5 xp pc's
    the rest are 98 anid ME's
    file server is ME

    #2
    When I had similar occurances using version 6 I reduced what I'll call the "refresh rate". From the main menu,,Other/Configuration/Network configuration.....check/adjust the value of "Update Records Every xx seconds", taking into consideration the number of users that may be working on the same record(s) simultaneously.

    FWIW

    TJ Baker

    Comment


      #3
      You need to turn off the windows opportunistic lock on all your workstations & server computers. Windows opportunistic lock is a windows registry setting. It locks files that are in use. This may sometimes have unwanted effects that may damage index & dbf files. There are utilities out there that will set windows opportunistic lock value from 1=ON to 0=OFF. After changing these values, each PC must be re-started. Good luck.

      RAWLINGS

      Comment


        #4
        98's

        does that work on 98 machines also. is there any chance for file corruption.

        Comment


          #5
          Win95, WIN98, & WINMe does not have the registry Opportunistic lock. Therefore noting should be done on PC's running those OS. Opportunistic lock
          feature are only on NT, 2000, XP, MS Server OS. Thanks.

          RAWLINGS

          Comment


            #6
            Re: config.sys and file locks

            There is a detailed discussion of this at

            http://www.kennedysoftware.ie/oldapps.htm

            under section

            "Registry Settings, Op-Locks, Write-Cache & Flush-Buffers under W2K/XP:"

            There is even a file, "oplocks.reg", that does the registry updates--not only for opportunistic locking but for other XP/2K command line anomalies.

            Of course, use at your own risk, but we have used this file in over 30 commercial systems without any problem.

            Jim

            Comment


              #7
              Re: config.sys and file locks

              I have a slightly related question. Is there a way to apply an opportunistic lock to a file without opening the file in its native application. Here is the scenario. We are working with files over a VPN. This is very slow. What we want to do is have the file "checked out" by applying an opportunistic lock to the file. That person would apply the lock, and download the file to their local machine. They would work on it locally. Once the person is done with the file, they would upload the file back to the server. At that point, the file would not have the oplock on it and every thing would be business as usual.

              Any suggestions?

              Comment

              Working...
              X