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

table change and multiuser problem

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

    table change and multiuser problem

    I have been trying to implement multiuser error handling for several scripts that I have written. However, when any of them attempt to execute the change_begin() function when the record is locked by another session or user, the script will "hang" and a5 will freeze. Apparently, the error is not thrown. The script will continue to hang until the record is unlocked. Then it will finish executing normally. Here is a small test script I wrote to confirm the problem I have encountered in my other scripts,

    option strict
    option nobreak

    dim orders as p

    orders = table.open("orders.dbf")
    orders.fetch_first()

    on error goto RECORD_LOCKED
    orders.change_begin()
    on error goto 0
    orders.repid = "01"
    orders.change_end(.T.)

    orders.close()

    end

    RECORD_LOCKED:
    on error goto 0
    ui_msg_box("Box", "Record locked by another user.")
    end

    Now, if I purposely attempt to modify the first record in the orders table in another session and execute this script, the script will hang when it attempts to execute
    "orders.change_begin()". Any ideas on why this is happening?

    #2
    RE: table change and multiuser problem

    Greg

    When a record is open in change or enter mode, it is locked to all other users. Alpha, like most databases, locks on the record level, that is, it locks one specific record only. As long as that record is in change mode, no other user can make a change. As soon as the record is saved, then another user can edit. Other users can view the record, but can't edit.

    Some scripts may open a table in exclusive mode. In that case, the whole table is locked. Normally you wouldn't want to do this, although some processes, like packing require exclusive access.

    This normally isn't a big issue even in large networks as it is not normal for more that one user to be editing the same record.

    Jerry

    Comment


      #3
      RE: table change and multiuser problem

      Your program probably is working, you are just not waiting long enough for the results. Wait at least one minute.

      Try this for faster results:

      option strict
      option nobreak
      dim orders as p

      orders = table.open("orders")
      orders.fetch_first()
      if orders.is_record_locked() then
      goto record_locked
      end if

      orders.change_begin()
      orders.change_end(.T.)

      orders.close()
      end

      RECORD_LOCKED:
      on error goto 0
      ui_msg_box("Box", "Record locked by another user.")
      end

      Comment


        #4
        RE: table change and multiuser problem

        Thank you for your solutions. I was not aware that the
        is_record_locked() function existed. I have tested it with my scripts and it works great.

        Comment

        Working...
        X