>>There was a thread on something like this a while back -- one way to deal with properties that "slip off" is just to add some code to enforce what you want, like Readonly = .T., Enabled = .F., etc. -- if you can't figure out easily why the properties are changing. I've had several like this.
>
>Bruce,
> I would hope that something is changing ReadOnly that I am just missing, as "slipping" properties is not an encouraging thought about an application tool from the world's biggest software company. Thnaks for the advice.
>
>Jim

That's so, but...we all know there are a "couple" of bugs in VFP 3, and MS acknowledges this, they rushed their product a bit. In more detail, there are two types of "slippages" I've found:

1) The kind that you are experiencing, perhaps...something that is done more-or-less by design, but perhaps wasn't designed as well as it could be, since a number of users have been confused by it...

2) The kind that are not by design, such as my listbox 3D for one source type that slips off if I don't reset it in code. I'm not even sure this is VFP's fault, it could be something in my Win 95...but there are a couple of this type (2) documented in the KB...

Anyway, I've worked around them with an occasional code resetting...