>Using ADO in the middle tier is something else - because then you don't have
UI to deal with
in a front-end situation, VFP's main advantage is it data binding (and I am
talkign here from the POV of application/products for large companies- not
a -all-in-one solution that fits to smaller one, there VFP has more
advantages) - its UI is slower than others, it does not use "real" windows
which makes it hard to have automated testing
<

I agree with you there the UI does make a big differance. I don't see data binding as Fox's biggest advantage on the front end though. Back in 2.x days we did not have it, yet it was still the best enviroment because of it's flexiblity. Now with (almost) full OOP, it makes it very powerfull. True a bit slower than some 'others', but with todays machines I don't see much of a differance. As for the "real" windows, you got me there, but would you rather design a complicated front end useing VB's flat class hirearchy?

>A workaround no matter how great is stil a workaround and is not as good as
a direct solution
and the fact that you can do something doesn't always mean it the best path
to follow
heck, I can run DOS applications and run them inside windows , but is this
the best way to design apps these days?
>
I agree with you on that point also, but remember just because it is a work around today does not mean it will be tomarrow. ALL languages have things that you must "work around", you just need to evaluate the trade offs and advantages dealing with that work around gives you. In the case of Fox I think it's other advantages out weigh and as long as the Fox community keeps pushing MS I think we will see what we need integrated in as a direct solution.