>Can you please explain further? Which methods and properties you normally use for common application ie add delete ... Whats wrong in using api functions. Although we can do it with pure fox code, using api is always very faster as well as reliable. It is always tested and so our testing time can be reduce.

I agree that API can be faster, but that in cases where you have to code a "workaround" using Fox, but in your case you have Fox functions directly related to the issue. I personally preffer using Fox stuff if it's already there, I'm not claiming one to be better than the other, it's personal choice that I've been happy with so far. By the way, if I remmember correctly, the example from Advisor was about Copy, Paste, Undo and Redo, iow related to text-editing not editing data. If your Undo button is ment to Undo edited text, than I will reccomend API approach, but "undo"ing a changed record involves revert the record in table, so I'm not so sure it will work as good on that.

Anything else?