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 another user changed the record.

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

    Error: Record was not updated because another user changed the record.

    I have an "Updateable" Grid component that connects to a Active-Link table (MySQL db). When I try to update any record, I get the following message and the update fails:

    Row 1: Record was not updated because another user changed the record. (Write conflicts found in these fields: member_last_name)

    When I try to delete the record, there's no error message but the record doesn't get deleted either. I have made sure that the particular table is not open in the Control Panel or the MySQL GUI (SQLyog).

    Can someone let me know the possible cause of this and it's solution?

    Thanks!

    #2
    Re: Error: Record was not updated because another user changed the record.

    I'm getting the same error, basically the same situation, except that the table is an A5 table. My app is in development so I know the only one in it is me, the tables are not open either.

    I've tried everything I can think of to fix this issue, but it still persists. The record to be updated actually gets updated, but the error message shows up.

    Any assistance anyone could provide would be greatly appreciated.

    I'm using version 9 application server, version 9 platinum desktop.
    Land of the Free, Because of the Brave
    Support our US Military

    Comment


      #3
      Re: Error: Record was not updated because another user changed the record.

      - Are you refreshing the grid and then getting this error?
      I sometimes got this error when I did.

      - Do you have the same grid open in more than one instance in your browser?
      Eric

      Alpha Five Websites
      longlivepuppies.com
      socialservicenetwork.com
      -------------------------------------------------
      socialservicenetwork.org

      Comment


        #4
        Re: Error: Record was not updated because another user changed the record.

        Hi Eric,
        In my situation the answers to both questions is No.
        Land of the Free, Because of the Brave
        Support our US Military

        Comment


          #5
          Re: Error: Record was not updated because another user changed the record.

          Im in the exact same situation, and both answers No as well.

          Comment


            #6
            Re: Error: Record was not updated because another user changed the record.

            Here is what my errors look like.

            Things are working mostly as expected, however this problem comes and goes...

            I'm the only one in on the site, and seems mostly to happen when I click the navigation bars at the bottom, and the sort columns.

            After is craps out, seems to wipe some of the data from the table in the database too... I have a number of checkboxes that I use as logicals, and they all get wiped back to blank (in the main table) (neither "T" or "F").

            Any tips on where to begin to diagnose this strange behavior?

            Thanks!
            Bill

            Comment


              #7
              Re: Error: Record was not updated because another user changed the record.

              Seems that it only goes haywire as soon as the Navigation buttons (bottom) are pressed to navigate to the next page... the thing that caught my eye was the length of the URL being passed... surely there is some sort of issue here... I suppose there are some sorts of limits to how much you can edit on a detail view grid?

              Here is what it looks like...
              http://localhost/ManageSolds.a5w?ManageSolds_Page=1&ManageSolds_Button_Submit=Submit&ManageSolds_FormInfo=%3CNew_Rows%3D0%3E%0D%0A%3CExisting_rows%3D5%3E%0D%0A%3Co%3Cr1%3CID%3D16%3E%0D%0A%3CPHONE_HOME%3D%22905-222-4555%22%3E%0D%0A%3CPHONE_WORK%3D%22551-111-1111%22%3E%0D%0A%3CPHONE_WEXT%3D%22%22%3E%0D%0A%3CPHONE_CELL%3D%22%22%3E%0D%0A%3CJC%3D.F.%3E%0D%0A%3CBRICK%3D.T.%3E%0D%0A%3CGO_BRICK%3D.F.%3E%0D%0A%3CBRICK_QTE_AMT%3D0%3E%0D%0A%3CBRICK_NOTE%3D%22%22%3E%0D%0A%3CGO_BRICK_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CFLATROOF%3D.T.%3E%0D%0A%3CGO_FLAT%3D.F.%3E%0D%0A%3CFLAT_QTE_AMT%3D0%3E%0D%0A%3CFLAT_NOTE%3D%22%22%3E%0D%0A%3CGO_FLAT_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CSHINGLEROOF%3D.T.%3E%0D%0A%3CGO_SHINGLES%3D.F.%3E%0D%0A%3CSHIN_QTE_AMT%3D0%3E%0D%0A%3CSHINGLE_NOTE%3D%22200%20year%20old%20home%2C%20remove%20slate%2C%20and%20garage%20roof%20too%22%3E%0D%0A%3CGO_SHIN_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CALUMINUM%3D.T.%3E%0D%0A%3CGO_ALUMINUM%3D.F.%3E%0D%0A%3CALUMINUM_QTE_AMT%3D0%3E%0D%0A%3CALUMINUM_NOTE%3D%22%22%3E%0D%0A%3CGO_ALUM_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CREPAIR%3D.F.%3E%0D%0A%3CGO_REPAIR%3D.F.%3E%0D%0A%3CREPAIR_QTE_AMT%3D0%3E%0D%0A%3CREPAIR_NOTE%3D%22Small%20corner%20piece%20missing%22%3E%0D%0A%3CGO_REP_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3E%0D%0A%3Cr2%3CID%3D10%3E%0D%0A%3CPHONE_HOME%3D%22905-788-7889%22%3E%0D%0A%3CPHONE_WORK%3D%22416-777-8855%22%3E%0D%0A%3CPHONE_WEXT%3D%222727%22%3E%0D%0A%3CPHONE_CELL%3D%22(999)%20999-9999%22%3E%0D%0A%3CJC%3D.F.%3E%0D%0A%3CBRICK%3D.F.%3E%0D%0A%3CGO_BRICK%3D.F.%3E%0D%0A%3CBRICK_QTE_AMT%3D0%3E%0D%0A%3CBRICK_NOTE%3D%22%22%3E%0D%0A%3CGO_BRICK_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CFLATROOF%3D.T.%3E%0D%0A%3CGO_FLAT%3D.F.%3E%0D%0A%3CFLAT_QTE_AMT%3D0%3E%0D%0A%3CFLAT_NOTE%3D%22%22%3E%0D%0A%3CGO_FLAT_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CSHINGLEROOF%3D.T.%3E%0D%0A%3CGO_SHINGLES%3D.T.%3E%0D%0A%3CSHIN_QTE_AMT%3D13400%3E%0D%0A%3CSHINGLE_NOTE%3D%22Front%20of%20Home%20only%22%3E%0D%0A%3CGO_SHIN_DATE%3D{01%2F20%2F2009}%3E%0D%0A%3CALUMINUM%3D.T.%3E%0D%0A%3CGO_ALUMINUM%3D.T.%3E%0D%0A%3CALUMINUM_QTE_AMT%3D450%3E%0D%0A%3CALUMINUM_NOTE%3D%22Front%20%20porch%22%3E%0D%0A%3CGO_ALUM_DATE%3D{01%2F20%2F2009}%3E%0D%0A%3CREPAIR%3D.F.%3E%0D%0A%3CGO_REPAIR%3D.F.%3E%0D%0A%3CREPAIR_QTE_AMT%3D0%3E%0D%0A%3CREPAIR_NOTE%3D%22%22%3E%0D%0A%3CGO_REP_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3E%0D%0A%3Cr3%3CID%3D11%3E%0D%0A%3CPHONE_HOME%3D%22905-444-5555%22%3E%0D%0A%3CPHONE_WORK%3D%22444-555-5556%22%3E%0D%0A%3CPHONE_WEXT%3D%222708%22%3E%0D%0A%3CPHONE_CELL%3D%22%22%3E%0D%0A%3CJC%3D.F.%3E%0D%0A%3CBRICK%3D.T.%3E%0D%0A%3CGO_BRICK%3D.F.%3E%0D%0A%3CBRICK_QTE_AMT%3D0%3E%0D%0A%3CBRICK_NOTE%3D%22%22%3E%0D%0A%3CGO_BRICK_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CFLATROOF%3D.T.%3E%0D%0A%3CGO_FLAT%3D.F.%3E%0D%0A%3CFLAT_QTE_AMT%3D0%3E%0D%0A%3CFLAT_NOTE%3D%22%22%3E%0D%0A%3CGO_FLAT_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CSHINGLEROOF%3D.T.%3E%0D%0A%3CGO_SHINGLES%3D.F.%3E%0D%0A%3CSHIN_QTE_AMT%3D0%3E%0D%0A%3CSHINGLE_NOTE%3D%22%22%3E%0D%0A%3CGO_SHIN_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CALUMINUM%3D.T.%3E%0D%0A%3CGO_ALUMINUM%3D.F.%3E%0D%0A%3CALUMINUM_QTE_AMT%3D0%3E%0D%0A%3CALUMINUM_NOTE%3D%22%22%3E%0D%0A%3CGO_ALUM_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CREPAIR%3D.F.%3E%0D%0A%3CGO_REPAIR%3D.F.%3E%0D%0A%3CREPAIR_QTE_AMT%3D0%3E%0D%0A%3CREPAIR_NOTE%3D%22%22%3E%0D%0A%3CGO_REP_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3E%0D%0A%3Cr4%3CID%3D7%3E%0D%0A%3CPHONE_HOME%3D%22(456)%20665-4455%22%3E%0D%0A%3CPHONE_WORK%3D%22%22%3E%0D%0A%3CPHONE_WEXT%3D%22%22%3E%0D%0A%3CPHONE_CELL%3D%22%22%3E%0D%0A%3CJC%3D.F.%3E%0D%0A%3CBRICK%3D.T.%3E%0D%0A%3CGO_BRICK%3D.F.%3E%0D%0A%3CBRICK_QTE_AMT%3D0%3E%0D%0A%3CBRICK_NOTE%3D%22%22%3E%0D%0A%3CGO_BRICK_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CFLATROOF%3D.T.%3E%0D%0A%3CGO_FLAT%3D.F.%3E%0D%0A%3CFLAT_QTE_AMT%3D0%3E%0D%0A%3CFLAT_NOTE%3D%22%22%3E%0D%0A%3CGO_FLAT_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CSHINGLEROOF%3D.F.%3E%0D%0A%3CGO_SHINGLES%3D.F.%3E%0D%0A%3CSHIN_QTE_AMT%3D0%3E%0D%0A%3CSHINGLE_NOTE%3D%22%22%3E%0D%0A%3CGO_SHIN_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CALUMINUM%3D.T.%3E%0D%0A%3CGO_ALUMINUM%3D.F.%3E%0D%0A%3CALUMINUM_QTE_AMT%3D0%3E%0D%0A%3CALUMINUM_NOTE%3D%22%22%3E%0D%0A%3CGO_ALUM_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CREPAIR%3D.F.%3E%0D%0A%3CGO_REPAIR%3D.F.%3E%0D%0A%3CREPAIR_QTE_AMT%3D0%3E%0D%0A%3CREPAIR_NOTE%3D%22%22%3E%0D%0A%3CGO_REP_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3E%0D%0A%3Cr5%3CID%3D9%3E%0D%0A%3CPHONE_HOME%3D%22(333)%20333-3354%22%3E%0D%0A%3CPHONE_WORK%3D%22%22%3E%0D%0A%3CPHONE_WEXT%3D%22%22%3E%0D%0A%3CPHONE_CELL%3D%22(444)%20444-4445%22%3E%0D%0A%3CJC%3D.T.%3E%0D%0A%3CBRICK%3D.T.%3E%0D%0A%3CGO_BRICK%3D.T.%3E%0D%0A%3CBRICK_QTE_AMT%3D5500%3E%0D%0A%3CBRICK_NOTE%3D%22%22%3E%0D%0A%3CGO_BRICK_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3CFLATROOF%3D.T.%3E%0D%0A%3CGO_FLAT%3D.T.%3E%0D%0A%3CFLAT_QTE_AMT%3D4400%3E%0D%0A%3CFLAT_NOTE%3D%22%22%3E%0D%0A%3CGO_FLAT_DATE%3D{01%2F27%2F2009}%3E%0D%0A%3CSHINGLEROOF%3D.T.%3E%0D%0A%3CGO_SHINGLES%3D.T.%3E%0D%0A%3CSHIN_QTE_AMT%3D6000%3E%0D%0A%3CSHINGLE_NOTE%3D%22%22%3E%0D%0A%3CGO_SHIN_DATE%3D{01%2F27%2F2009}%3E%0D%0A%3CALUMINUM%3D.T.%3E%0D%0A%3CGO_ALUMINUM%3D.F.%3E%0D%0A%3CALUMINUM_QTE_AMT%3D900%3E%0D%0A%3CALUMINUM_NOTE%3D%22%22%3E%0D%0A%3CGO_ALUM_DATE%3D{01%2F27%2F2009}%3E%0D%0A%3CREPAIR%3D.F.%3E%0D%0A%3CGO_REPAIR%3D.F.%3E%0D%0A%3CREPAIR_QTE_AMT%3D0%3E%0D%0A%3CREPAIR_NOTE%3D%22%22%3E%0D%0A%3CGO_REP_DATE%3D{%20%20%2F%20%20%2F%20%20%20%20}%3E%0D%0A%3E%0D%0A%3E%0D%0A%3Cpk%3Cr1%3Ckey_1%3Cvalue%3D15%3E%0D%0A%3E%0D%0A%3E%0D%0A%3Cr2%3Ckey_1%3Cvalue%3D10%3E%0D%0A%3E%0D%0A%3E%0D%0A%3Cr3%3Ckey_1%3Cvalue%3D11%3E%0D%0A%3E%0D%0A%3E%0D%0A%3Cr4%3Ckey_1%3Cvalue%3D7%3E%0D%0A%3E%0D%0A%3E%0D%0A%3Cr5%3Ckey_1%3Cvalue%3D9%3E%0D%0A%3E%0D%0A%3E%0D%0A%3E%0D%0A

              Comment


                #8
                Re: Error: Record was not updated because another user changed the record.

                Are you doing something to cause that long URL? If so what, and what are you trying to accomplish. Under normal conditions, the Next buttons are just a short string like this: "portfolio.a5w?portfolio_Page=2&". Max URL's are just above 2000.
                Steve Wood
                See my profile on IADN

                Comment


                  #9
                  Re: Error: Record was not updated because another user changed the record.

                  Hi Steve,

                  I have no idea what/how those long URLs are being generated. It is totally unintentional. I guess I must have flicked the wrong bit somewhere! But which one?

                  Is that because it is an updatable grid, and it's posting back all the values in the grid?

                  Thanks,
                  Bill

                  Comment


                    #10
                    Re: Error: Record was not updated because another user changed the record.

                    Maybe you can upload the grid component here and let us test. I've never seen a URL of any great length for navigation.
                    Steve Wood
                    See my profile on IADN

                    Comment


                      #11
                      Re: Error: Record was not updated because another user changed the record.

                      Thanks Steve,

                      Seems all one has to do is change 1 piece of info in the grid, hit "Submit", then when you mouseover the nav-button at the bottom of the page, you'll see the URL to go to the next screen is super-long.

                      The entire project is at:
                      http://msgboard.alphasoftware.com/al...5&d=1233153560
                      http://msgboard.alphasoftware.com/al...6&d=1233153560

                      Comment

                      Working...
                      X