Yeah, me too, Sergey. As well as @...MENU. I had this architecture where the screen layout was totally in metadata and was painted when a module was called by SELECTing into the metadata table with the module ID as a parm. Needless to say, the approach was not popular with maintenance developers at the client site :-)

I was the type who wouldn't let the backgrouind processing do squat...I had to have total control over UI and back code. Perhaps that's why my travails with.Net are so painful.

BTW, see you in March (bseg)

>Neither did I. :)
>But I remember building quite complicated screens in FPD 2.0 with @..SAYs and GETs
>
>>Although I have to say that I never used the FMT myself; I preferred to paint the @..SAYs and GETs manually in a DO WHILE loop in a PRG. LOL. Old times, old people ;-)
>>
>>>Hi Mike,
>>>
>>>The .PRX is compiled FoxPro file format (.FMT) used in FoxPro 1.0 and earlier, before Screen Designer was introduced in FoxPro 2.0. Type in the Command Window
>>>

>>>SET FORMAT TO ?
>>>

>>>
>>>
>>>>Go to:

http://dotwhat.net/prx/4341/

>>>>
>>>>It says that PRX is a Compiled program file extension. What version of FoxPro used this as a file extension for a compiled program?
>>>>
>>>>Just curious..