>Hi,
>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 ?

To the other comments, I want to add that VFP treats variables as an interpreter does, not as a compiler. This is not serious in practice, but it does have two drawbacks:

1) Often you only get an error message at runtime. It helps to develop better programs if errors appear already when you compile a program.

2) Since VFP has to loop up variables in its table of variables, working with variables is slower than with a "real" compiler.

3) The fact that all variables are of type "variant" also both makes the program slower, and can produce errors at run-time (type mismatch).

Some of these things, I think, have been changed in VFP 7 - specifically, I understand that you can specify the type of a variable.

None of these problems are extremely serious, and the way variables are handled gives you some flexibility not available with a "real" compiler.

Hilmar.