Tracy,
I certainly understand the need for porting to VFP. We're completely redesigning our product for standalone, LAN, and web operation. We will be using Web Connection on our web site to support remote clients. We currently have over 12,000 users of our product. We started out in 1981 on Apple IIe's and then migrated to FoxBase...FoxPro DOS...FP Windows and now VFP. It's been an interesting ride. ;-)

If you see any posts or articles concerning FP2.6 migration to VFP please drop me a line at kpenrod@classplus.com.

Thanks,
Ken


>>Thanks, Tracy,
>> I may try this approach and replace a few of the forms we're having problems with. It certainly wouldn't hurt to try.
>>
>> Do you know if any other UT members are doing similar type workarounds with FP2.6 to VFP?
>>
>>Ken
>
>snip
>
>Ken, I have no idea, but there must be others. Maybe some of them will jump in here and respond. I know the best idea is to do the entire project from scratch in VFP (except where you can cut/paste and use the same functions/prgs/etc) whenever possible. However, there are times when business requirements preclude that which is what happened in our case. We had to have the app available in VFP in order to take advantage of the newer printers, USB ports, communications in windows, link to our web apps, etc when required. That's why it is working the way it is-ported over little by little. We chip away at the dos screens and reports little by little porting them over to VFP. It is a long process when you have a HUGE app used by over 500 customers that took 10 years of programming in FPD26 to reach fruition! One of our other apps is used by over 700 customers (it is already ported to windows) and the customer base for both keep growing!
>
>Good luck in your endeavors!
>
>Tracy