>>>>Hi everybody,
>>>>
>>>>I raised this problem once already, but would like to discuss it again.
>>>>
>>>>If the user changed someting in the form, but then changed his/her mind and removed the change, the GetFldState function would anyway report this record as changed. How do you solve this problem in your applications? Are you triggering all the logic, which is triggered when the user really changed something? Or you're not using GetFldState function (GetNextModified)?
>>>>
>>>>In our case we're using the framework. So, if we want to implement different way of detecting the change, it would be a complicated task.
>>>>
>>>>Thanks in advance.
>>>
>>>I am using GetFldState with no additional logic to see if something is REALY changed. BUT different users can't work on same records.
>>
>>Thanks. So, if you added a new record, typed something, then removed, what you just typed, then press Save button, then all the logic is going to be executed.
>>
>>In my opinion, it's wrong. You didn't REALLY change anything.
>>
>>My colleague, though, used this terminology: this is not a playground, so if the user touched the keyboard, he/she should live with the consequences...
>>
>>So, in your opinion, we should not try to spent our efforts on working around this problem, right?
>>
>>Thanks.
>
>
>Your colleague thinks exatly as me :o))
>Can you count how many hours you will spend to resolve this problem? I think these hours can be spended for future development of the application, add a new special, or not so special, features in the application that makes users live easier.

Thanks, Borislav. I guess, we'll give this problem a lower priority and put it in "to do not in the nearest future" list < g >