>Yes I did it.
>But this formula gives coordinates only approximatly, not exactly.

How exact do you need the coordinates? You can use the properties of teh columns to determine where things are. If the user moves a column the column's ColumnOrder protery will reflect the change. If you can tell us what you need to do with the textbox coordinates then we could better explain how to determine them. BTW, the textbox is at 0,0 within its cell.

I tried your test and I do not get any corruption.

>Use buff 3, have grid in form and couples fields with controlsorces.

One thing I do is ALWAYS use buffermode 5. I never use row buffering especially in a grid where recor dpointer movement is very easily caused by accident.

>Have button with code =tableupdate(.f.,.t.)

Secondly, I never use .T. to force a tableupdate. I wnat VFP to tell me when there is an update conflict.

I alos ALWAYS check the return value form TableUpdate(), even with the force argument TableUpdate can still fail for reasons other than Update Conflict.

>Do you see anything strange in the grid. Any fake tweens, you will not be able to navigate through it)??

I am not sure what you mean by "fake tweens". Anyway I didn't see anything out of the ordinary.

>I observe index content destruction!!!!

Index destruction can be causedf by many different things, abnormal system shutdown, bad netwoprk connection, bugs in network client software, etc.