>
>I have heard here that you can even get sued by some offended client for 'misguiding' them into purchasing your VFP application
I think I'm the only one who has mentioned getting sued in this thread so just in case this is a reaction to my comments I'd just like to clarify I said I be very reluctant to advise a client to put their back end data in DBFs vs SQL Server - and that was in the context of VFP apps. Very different from implying I would be misguiding clients if I got them to purchase a VFP applicaiton.
VFP DOES NOT REQUIRE DBFS !!!! <bg> and it is my position that implying the two are necessarily joined at the hip is one of the problems we have in maintaining acceptance of VFP in many environments. Well designed VFP apps with a SQL data store can be supplemented rather than replaced by modules in other languages for web, mobile, reporting etc. and give clients a better path for evolving while still using the sound, fast VFP app they invested in.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
