>>But, Robert, I also need to use VFP 7 for an existing client. <<
Why?




>>Good email!
>>One word for a VFP developer who doesn't upgrade to VFP8. IDIOT!
>>
>>
>
>But, Robert, I also need to use VFP 7 for an existing client. What do you recommend that I do?
>
>
>Please answer that before you call me an idiot.
>
>Thank you.
>
>
>
>>
>>>Hi Guy,
>>>
>>>>I love VFP. And I think v8.0 is awesome. Isn't it?
>>>
>>>Yes it is.
>>>
>>>We put a lot into VFP 8 that helps you sell to your clients. Themes, tab orientation, combobox images, and other UI enhancements that you can razzle-dazzle clients with.
>>>
>>>On top of that, we added code references, the taskpane and other productivity enhancements for you guys, the developers.
>>>
>>>Was that it? No. We added the ability to subclass pages, optionbuttons, and other member classes. We gave you the ability to create dataenvironment classes. VFP now supports Collections - giving you great OOP functionality. And native event binding ... think of the possibilities!
>>>
>>>Could there be more? Yep. How about TRY..CATCH? How about autoincrementing fields which enhance your ability to develop and maintain normalized database applications. How about more detailed error messages to help you debug your applications?
>>>
>>>And more? Yes. How about CursorAdapters and XMLAdapters? These two classes allow you to completely rethink VFP-based systems architecture for scalable applications.
>>>
>>>How do I use this stuff? Well, check out Help. There were hundreds, maybe thousands of Help topics revised - a lot of them by experts in the community with real world examples. Walk-throughs were edited or added to help guide you through new stuff.
>>>
>>>On top of all of this, many bugs were squashed - some going back to the primordial ooze of VFP (version 3 or 5).
>>>
>>>Are there still bugs? Well, of course there are. There's no application in the world that is completely bug free. But we're pretty sure we've found and killed the majority of showstoppers (AKA C5s).