><snip>
>
>>Hi Alex,
>Just remember that if it's a one off conversion - its possible to write code in the same way as 2.6 does it. Just need to recreate all the screens - ignore all the fancy new features like dataenvironment/buffering etc. Most of the old code will work just fine. Each screen should then have a .prg "wrapper" where you declare and scope form level variables. (But at least subclass the VFP base classes one level - even if they are a direct copy)
>>Dave
>
>two questions. keep reading in UT about "wrapper", what does that mean?
>
>second, when i convert from 2.6 to 5.0, should i choose visual or functional conversion? i converted a ton of programs awhile back and can not remember what i choose. what is the difference between visual and functional?
>
>thanks - brenda

Here's a simple example

main program.....
Do Customer.prg

customer.prg...
PRIVATE myvariable
DO Form Customer
FUNCTION NiceName
RETURN TRIM(Customer.First) + ' ' + Customer.Last
...............

So you see customer.prg is a wrapper for the customer form, where you can declare variables that are scoped for the entire form, and have procedures/functions callable from anywhere in the form.
It's not OOPs though, but's thats how many of us did it in 2.6
HTH