I have to comment on the reoccuring concern about VFP. After too many years in this business I have seen and participated in similar discussions about other languages. The most notible may be PICK. Quickly it was (IS) a very relational like, imbeded data dictionary, transaction oriented language/DBMS/operation system first built for the Navy. Lots of users/developer loved it, but it was 'not mainstream' and 'a little wierd'. Debate continued for YEARS about how it was going to die, developers would drop out of sight, and would never be supported by anyone again. Since it's a good tool for certain application classes, guess what, it lives in unix and IBM/VM environments and is still used for large insurance and banking systems. Similarly were concerns about PL/I, SAS (yes at one time who would have wanted to use a statictical system to build data warehouses), smalltalk, etc. My point is that good tools (like VFP) tend to live because their good tools and heavy used by the people who actual pay the bill - end users/client companies. IBM tried to kill VM since CMS escaped from the Cambridge Labs and finally gave up and guess what, it's now in the hardware microcode for SYSPLEX/MultiImage systems - their flagship offering. So, use what make sense and not to worry to much. I just had to write a small VB5 frontend for a existing VFP app - not fun but all the concepts still apply even though I had to 'create' some VFP like structures (by the way VB's idea of classes is truely bizzare).
IMO
:))
Gary