We haven't checked it yet, we have been working on it for only an hour or so...

You guys were right about the fact that it was a lockscreen problem though. I have put a lockscreen = .f. at the end of the init of a few form and they started to work fine. The funny thing is that lockscreen was already .f. it seems that colleague's machine does not "catches" the lockscreen is .f. and the screen stays locked. So I have to tell it again that it is .f. I say that because I absolutely did not have this problem on my machine. Everything was and still is working fine. I really hate having to do that kind of patch...

I'll look into it a bit further...

This is really weird!!!

>Hi Eric,
>Looks like a different problem altogether. Did you check whether this app works on another machine? This way you'll know whether the problem is coming from the app or the operating system.
>
>>That's not it, I checked and the forms that do not work have lockscreen=.f. by default.
>>
>>Some forms that appear correctly 30 minutes ago do nt appear correctly now. And some controls are available even if we do not see them. (We can type in a textbox and click the close button even if we do not see it...)
>>
>>
>>>Hi Eric,
>>>
>>>I had seen the same problem when converting apps from VFP3.0 to 5.0. The forms and form classes had Lockscreen=.T. as default. Maybe it is the same problem which is coming up...
>>>
>>>>Hi Everyone.
>>>>
>>>>We have an application which was created in VFP 5.0. We decided to upgrade it in VFP 6.0. It worked fine until we tried the application on my colleague's computer which is a Windows NT Server 4.0 with service Pack 3.
>>>>
>>>>The problem is quite simple to describe. Some forms are Transparent when we execute the application. I mean litterally transparent. The controls are not available, all we see is the frame of the form.
>>>>
>>>>Could anyone help...