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

ERROR: Record was not updated because of a write conflict

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

    ERROR: Record was not updated because of a write conflict

    I often have users get a write conflict error:

    Field Name: FName
    Current Value Stored in Table: M
    Original Value in Field: bj

    It's not because someone has changed the record while this user was also changing it. It happens to often and users are not in each others record. I think it's happening when users change a record, submit it then go back into a detail view and edit something then submits again.

    I've had been getting these error a lot on date fields, so unchecked the "Check for write conflicts" for those field. But it also happens on simple nvarchar fields and it doesn't seem like a good practice to just uncheck "Check for write conflicts". It SQL.

    IE it the browser being used. I can't recreate it but it happens a few times a weeks. There are about 25 users.

    #2
    Re: ERROR: Record was not updated because of a write conflict

    Are they hitting the submit button more than once? Happened with our app on some components with lots of validation rules and AfterUpdateRecord Event, so I put a Javascript System Event on it to show a pop-up box just so the user knows they did indeed hit the button the first time...

    Comment


      #3
      Re: ERROR: Record was not updated because of a write conflict

      I just turn off the check for write conflicts in the grid property in all of my grids
      Cheers
      Mauricio

      Comment


        #4
        Re: ERROR: Record was not updated because of a write conflict

        Originally posted by mmaisterrena View Post
        I just turn off the check for write conflicts in the grid property in all of my grids
        I did that too, but I think this is more a bypass than a solution.
        So, I am very interested in the Why of this behaviour.
        Ren�
        Windows 7, V11

        Comment


          #5
          Re: ERROR: Record was not updated because of a write conflict

          Originally posted by Ren� Stout View Post
          I did that too, but I think this is more a bypass than a solution.
          So, I am very interested in the Why of this behaviour.
          This thread might give the answer.
          Ren�
          Windows 7, V11

          Comment


            #6
            Re: ERROR: Record was not updated because of a write conflict

            Thanks for the help. I am turning off the Check for Write Conflicts option for the entire page as users let me know they are have a problem on that page but I'm not comfortable with it.

            I pretty confident the users are getting these errors even when no one else has changed data in that record. Users are getting these errors on nvarchar, bit and date field. It could be that they are clicking Submit...

            If anyone comes up with a reason for the error let me know so I can fix the problem then turn back on the Check for Write Conflicts.

            Thanks.

            Comment


              #7
              Re: ERROR: Record was not updated because of a write conflict

              uncertain that my situation is the same as anyone else, but I was able to stop my write conflict. I obviously caused the conflict.

              My Detail section updateble text field had the Display Format set to uppercase the entry for Display.
              I also had created code in the CanUpdate and CanInsert to uppercase the field so that it would store uppercased data.
              To top it off i also had another longer text field into which the user could enter data via a barcode scan.
              Then I executed javascript in the OnChange to parse out the scanned data field into three fields (my one text field and two number fields) and updated those fields with {grid.Object}._setValue . This provided the user a choice to scan in the data and not have to enter, but they would tab through the fields automatically filled in by the parsing javascript. If need be, they could also manually alter the text field with either upper or lower case.

              I am not certain I can reason it out how the conflict occurs but the warning message would show the same text content but 'current' as lower and 'original' as upper.

              So by eliminating Display Format (which was trying to display uppercase string in the field and fighting my other functions) the write conflicts stopped.
              Hope this helps someone.
              Last edited by otto17; 05-25-2012, 03:51 AM.

              Comment

              Working...
              X