>How you prefer. I didn't say validation on/off though.
>Cetin

Not sure, I understand, what do you mean. Here is Validation Rule for the record:
IIF(VARTYPE(ovalid)#"O".OR.Ovalid.nlocked<0,.F.,IIF(Ovalid.nlocked=0,.T.,bldmstrtr("table")))

I have oValid instantiated and oValid.nLocked = 0, so it would return .t. on each record. When I added "set step on", I noticed, that myForeColor and myBackColor methods of the grid were firing. I guess, it's because tableupdate moves the record pointer, which in turn invokes AfterRowColChange, which causes firing of these methods. Anyway, thisform.lockscreen = .t. during save should prevent this from happening, I hope.

There is another big problem with our Add (Save) method. I found, what it returns .F. in couple of places before finishing all its logic. So, I hit Save without doing anything on this form, and my Save button didn't become 'Add' due to incorrect code in Add method.

>>Hi Cetin,
>>
>>Actually, I think, I found couple of problems.
>>
>>First of all, I had some custom method for ForeColor and BackColor in the grid. I added LockScreen to prevent updating screen. I also found bunch of problems with our framework Add method (it serves double duity Add/Save depending on EditMode). Unfortunately, I'm not in charge of our classes code, so I reported this problem to my colleague, but she is leaving, so I don't know, how long I need to wait for resolution...
>>
>>Validation was turned off, so it should not be a problem...
>>
>>>>Hi everybody,
>>>>
>>>>I have a file with 6832 records. I've changed one field in 4734 records and pressed save button. Form has a grid. These 4734 records are filtered. I see a wait window 'Saving...' for about 10 minutes now. Last time I hadn't patience to wait, so I interruped. What could be a problem, why does it save each record for so long? This field doesn't have Field Validation Rule, but record has Record Validation rule.
>>>
>>>Before anything else I'd validate database.
>>>Cetin