Hi, John

The easist way to do this is to go into the form.refresh method and put code to make a textbox.enabled set to .T.
But if you are trying to make an actual field in the table editable. I would ask why? The user should not be able to edit any fields, unless you are ready to be able to save that info.
If the field you are talking about is just a textbox for look up or such, it should not be enabled during edit mode, because it could move the pointer off the record in the table and you will not be able to do a good save on it.

Hope this helps.
Beth
>Jison,
>
>Thanks very much for your reply, but as I said, I'm very much a VFP rookie. I don't know how what it means to look at the "class created by the wizard then follow the event." Is there a simple way to find what, exactly, is making this new field inaccessible until the "edit" button is clicked? Is there something I can change in the button or in the new field itself? I've opened the "Properties" box for each and searched through every tab (Data, Methods, Layout & Other) but don't see anything that looks like it's having this effect.
>
>Thanks all,
>
>John
>
>>Hi john,
>> when you use wizard in your data entry, it will a class derived from FFC . try check at the ur class created by the wizard then follow the event.
>> Another method it to create a textbox class then drop it on your form. because i guess internally the wizard use setall() your custom class will excempted in this case.but its not a good idea. mudify your class generated by wizard would be better.