>I've been recommended that this is a good place to find experts in Visual Foxpro. My boss has given me the task of evaluating Visual Foxpro for possible new jobs. He's had one or two people say how good it is &, being on the nervous side for using new stuff, he wants me to find out what is bad about it. So I thought I'd try asking the real users of the product. I assume the majority of people here will be able to tell me all sorts of good things, but just like that awful interview question "And now tell me about your worst qualities", I'd like to pose the same question about Visual Foxpro. What is going to make our lives difficult if we chose Visual Foxpro ?

I think you should evaluate development tools in relation to the requirements of the "job". Whatever is "good" or "bad" about VFP may be totally irrelevant to the task at hand.

"Everybody" will tell you how "bad" Access is; however, it may be perfect for the current job.

The "worst" thing (IMO) about VFP is that it is a "fringe" product. If a requirement is that the final product must be maintainable, that implies that there be developers available (in the market) that can maintain it; these people may be hard to find (vs Access, VB, Java, etc.)

(The "usual" way one selects a development tool is to list the requirements of the job and beside each requirement list the "merit points" of each developemnt tool and then tally up the numbers and see which tool scores best.)