>>>Yes I saw them. What I can tell you. There is always issue of personal preference. If someone is comfortable with VB development environment then it's good for him/her and vice versa. I mean that qualified VB programmers and qualified VFP programmer will probably get similar results in regards to interface development. Now, in regard to query speed. You know the same results (from user's standpoint) can be reached by absolutely different queries. For example, I have two 50K tables (as you have) and I want to bring this data into grid. I can take it simple: make a join, run SELECT, get result. However, I can treat this situation quite differently: I can run query against one table (no joins) and will just diversify Grid.Column.ControlSource to SEEK in another table. Will this faster? Probably much faster. Should we blame or discuss MS role in this or have other global talkings? Probably not. >> >>You're absolutely right about personal preference. I do believe, however, the fact that I have been working with VFP for two years, and VB for two weeks, and that I can perform at almost the same speed in both, should have some bearing on the matter. One could argue that I'm just genetically predisposed <g> to VB development. On the other, it could be that the tools are more mature and make it easier for the developer. I cannot speak for Microsoft, of course, but it would be my place to recommend the most cost-effective solution to a problem to management in my company. If I could meet more deadlines using a different tool, so be it! >> >>For what its worth, I'm not knocking VFP as the most powerful relational database tool available. I'm just shocked and pleasantly surprised by what I've seen in the non-VFP world. I have no reason to be biased towards one or the other; if anything, the time I've invested in VFP should bias me to VFP! > >I didn't mean that you are biased. However, I wouldn't extend anyone's personal experience to all programming world. BTW, many people here also worked with VB, and sometimes more than two weeks:). Anyway, what do you think about practical part of my reply, i mean query/grid approach. One friend of mine (very good VB programmer) really disbelieve me when I tell him what I can do with VFP grid. What is your perception?

As someone who came from VB and moved to VFP 5.0 I can say that, for me, the learning curve in VFP was extremely short, compared with how long it took me to to learn VB. VFP definitely has a smoother connection to its backend, and there is nothing in VB that compares to the command box and direct table access. I think the speed in learning a second GUI frontend is reduced remarkedly if one has considerable experience in an other GUI frontend.
$ 0.02