>This has been a very interesting discussion I have been following, but it has proven one single thing only - you like VB over VFP. I say good on you, you've found your niche. I personally think that after you have had a little more than two weeks with VB, you may find it restricting too.
>
>I have been programming in Pascal since 1982 and Delphi since about 6 months before the release of Delphi 1. Hell, I was even a Borland Consultant for a little while. I personally prefer VFP for the work I'm doing even though VFP contains restrictions - actually VFP has quietly had many things that are considered "new and amazing" in Delphi 3. If I work with the restrictions in mind, then I can get a lot of work done in VFP with more maintainable and updatable code - and the user is happy. I couldn't believe the excellence of the Object implementation in VFP, even though I think that it could do with more work (roll on Tahoe).
>
>I have programmed in FoxPro since about 1991 and dBase before that so I'm not new to Fox, only VFP.
>
>Go with VB if you are more productive in it, I can't stand it but that's what personal preference is all about.
I believe that your argument is both relevant and cogent. I may find restrictions in VB once I experiement more. I suppose I was most pleased to find many of my "wishes" granted in VB; i.e. "I would have done it this way..."'s implemented in a fast, compact, easy to use package.
What I do wish is that VB has a better object model, which VFP definitely has (provided you figure out how to use their implementation correctly).
The most relevant statement you made actually was about working with its limitations in mind. If you "go with the flow", so to speak, of how VFP was designed to be used, it is a beautious tool.
