Joe (sorry Edward),

How are you invoking the form?

Are you in the development environment when this happens?

Is this a "main" form or some sub-form of the app?

Do you have any "odd" things like transparent cover-ups in operation here?

So far what I think I have is. . .

You have a single form, invoked in the development environment, which shows NOTHING unless you include a WAIT statement, and then you can see some *initial* things but you cannot see anything elsered or the results of clicks.

Is that it, or are there some missing details?

Cheers,
Jim N

>>Edward,
>>
>>No, my colors aren't the problem. If that were the case I would see anything in the field to begin with, and I CAN see whatever value happens to already be in the field.
>>
>>Here's another clue...
>>This form was formerly coming up BLANK. I'm talking no control, fields, boxes or ANYTHING visible...However, when I clicked on the place where my CANCEL button should have been - it worked!
>>
>>I noticed that simply by putting a WAIT WINDOW "xxx" TIMEOUT .5 in my ACTIVATE code, I am now able to see everything that is on the screen, BUT cannot "see" radio button changes or characters entered into fields (even though the values are saved when I exit the screen with a TABLEUPDATE)
>>
>>Don't give up on me yet!
>>
>>thanx,
>>Joe
>
>There too many strange things here. I remember you said that Form.LockScreen is Ok, so... Personally, I would prefer to recreate the form from scratch by tedious copying of controls and testing.