Hello Nerissa,
This error results when something is out of sync between your view and your (backend)table. When everything is working properly with your views and code, this should only happen when two users' entries conflict.

In this case, however, it sounds as if this new (and subsequently edited record) conflicts with itself. That could be caused by both code (e.g. moving a record pointer on a record-buffered view) or by a "bad" view definition. More than once, we've had to delete a poorly behaving view and reconstruct it from scratch.

Since you say the code is the same between your live and test system, I would suggest that you take Kevin's advice and retrace your steps directly in the view. Your best bet would be to do this both in the test as well as the "live" system to compare how they behave. If you don't see the same behavior, I would advise you to scrap the view and recreate it.

Hope that helps,
---J

>Hello to everyone,
>
>I am getting this error #1585 - Update conflict everytime I save (tableupdate()) the record that I am trying to edit. The error is found in our live environment. Even if I enter a new record, save it and edit it afterwards, I still get the error when I save it. I did the same scenario in the test side but everything works perfectly. So it is not because of only one record. But I just migrated the whole project in the live side. So the codes are really the same.
>
>I compared the definition of my view. Everything is the same. Then I checked the index of my table for this view. I don't see any difference as well. I recompiled all files again but I still get the error. What else could be the reason for this error?
>
>Thank you very much for any help.
>
>Nerissa