>>Anon,
>>
>>This does raise an interesting problem though, at least in my little mind. . .
>>If one sets the Enabled property(s) using some variable, and then whenever the variable changes one issues a ThisForm.Refresh() BUT NOTHING DIFFERENT RESULTS because the properties were not changed explicitly, then precisely HOW does Refresh() work???
>>
>>I don't remember the initial bits of this thread, but I have to wonder if possibly the problem is that "doedit" is *not* PUBLIC, so it is defaulting to .F. where ever it is used outside its defining/setting function(s).
>>
>No, it doesn't work then either, nor do other property variable redefinitions work in an implicit fashion, I've tried it before. I don't think it is the fault of refresh, it's just the way vfp works internally. I do think it would be nice feature...

*********
Infact, I tried to use the Setall method also, but once the record
navigation keys are disabled, refresh method doesn't enable them.
I am using these commands :-

[edit Click method)
doedit=.t.
thisform.setall(enabled,doedit) && enabling fields and grids
thisform.recmov.setall(enabled,!doedit) && disabling Record movement
thisform.refresh()

[save Click method)
doedit=.f.
thisform.setall(enabled,doedit) && disabling fields and grids
thisform.recmov.setall(enabled,!doedit) && enabling Record movement
thisform.refresh()

but once record navigation keys are disabled, nothing is happening
In my form, more then 30 fields are there, and I am planning to put
4 tabs, having fields from all the files. If I will set each and
every field manually, it will be very long. Pls Advs