Well of course. :o) *G*

>>Hi Bob,
>>
>>I already use the visual converter to convert our FPD26 screens to forms and then cut/paste the controls and fix them on a new form based on my base class. What I am referring to here is DEFINE WINDOW statements in prgs that include @..say and @...get statements on them for data collection. All of those must be changed to create a form also and it is much more time consuming working on those...
>>
>>Remember:
>>
>>

>>DEFINE WINDOW editwin FROM 2,6 TO 20+glRow,73 TITLE "LOSS NOTICE" FLOAT SHADOW FONT (glFontName), (glFontSize)
>>ACTIVATE WINDOW editwin
>>
>>@  1, 2 SAY com_name(mpo_insco(pol_number))
>>@  1,34 SAY "Policy #:"
>>@  3, 2 SAY "CSR:"
>>@  3,12 SAY "Trans-Date:"
>>@  3,36 SAY "Date of Claim:"
>>@  5, 2 SAY "Date sent...:"
>>@  5,34 SAY "How notice was sent:"
>>@  6, 2 SAY "Claim#......:"
>>@  7, 2 SAY "Adjuster....:"
>>*...
>>@  3,51 GET m.lossdate VALID vEpoch(@m.lossdate)
>>@  5,16 GET m.datesent VALID vEpoch(@m.datesent)
>>@  5,55 GET m.howsent
>>@  6,16 GET m.claimnum
>>@  7,16 GET m.adjuster
>>@  8,16 GET m.datepaid VALID vEpoch(@m.datepaid)
>>@  8,48 GET m.amtpaid PICTURE "@z 99999.99"
>>@  9,16 GET m.pmtfor
>>*...
>>READ CYCLE
>>
>>

>>Examples like the above (hundreds of them in our code) must be switched to forms...there are no .scx files for those because they were hand coded...
>
>I wrote such a parser once, I think in 1992, when we were moving from FP1.02 to FP2.0, and it was reading .prg files and creating .scx files (inserting records). Wasn't that hard to do. It was six companies ago and I don't have the source, but I still have the parts of Alejandro's converter (i.e. its proto version that I once wrote) which can be used to create the form, insert the controls, insert the DE (if needed), insert the code snippets as methods, and save as scx. So it takes just the prg reader part.
>
>I figure you expected me to jump in here, right? :)