I see,

We never coded like that. We always created a screen, and put the code in the cleanup snippet, or just called the program from the screen.

I don't know if there is a tool to do such a thing. Except, perhaps you could run the program and then 'save as class' the form while it is running. I haven't tried it, but it is a thought.

BOb


>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...
>
>>>Has anyone determined the easiest/fastest way to convert DEFINE WINDOWs in prgs that contain @...SAYs and @...GETs in FPD26 into VFP forms?
>>>
>>>TIA,
>>>
>>>Tracy
>>
>>Have you tried the VFP converter? A 'visual' conversion will convert the SCX to a form. The problem, it will use all base classes.
>>
>>BOb