Barbara,

Thanks for the suggestion. I still don't know why it was changing, but I was able to find a spot in the code that I could force it back. There didn't appear to be anything in the code that was directly affecting it. It just changed when it wanted to. Fortunately, I was able to "force" it in the Refresh. I know it's just a work around until I have some more time but at least I can move forward from here ;-).

I like the language, but it "feels" harder to track down problems. I guess like FPW, it just takes time to get used to the debugging tools available to you. I really like the ability to go into design mode while suspended out of the application. That alone has saved hours already!

Sorry for rambling. Have a Merry Christmas and a Happy New Year (only 2 more until the fun starts!),

Rod Lewis



>>Hi,
>>
>>I've been getting into VFP now for a few weeks and am running into an inconsistency from one screen to another. The problem is in a screen with a grid that allows entry into one field. I set up a new class that has a property for the frozen column. All columns come are populated with a default option of disabled and readonly. In the Init of the new grid class I set up the frozen column to be .Enabled = .t. and .ReadOnly = .f. Everything works great most of the time, but on one out of 3 screens, the CurrentControl for the column has .ReadOnly = .t. This causes a major headache when you want to edit the field. I can't figure out where it's being set. I can even copy the grid from a screen (sorry form) that it is working in to a new screen, don't change anything, and in the second screen it no longer works.
>>
>>Every time I think I've got it figured out, it happens on the very next screen. I rewrite all of my classes and then it works again for a couple of screens.
>>
>>If you need more information, let me know and I'll share whatever you need.
>>
>>TIA,
>>
>>Rod Lewis
>
>Don't you hate problems like that? :-((
>
>Try following the code in Debug with a breakpoint set for the Readonly property. It looks like it's being re-set somewhere in your form.
>
>Barbara