I absolutely agree with you in that, I never saw it for the point of view of big applications, I took it as the small application experience
I had with FOXPRO, I am completely sorry for that, I must admit that VFOX as well allow me to work with big APP, but MICROSOFT needs to create a .NET version for FOX or something, it necessary, my opinion came to the scene cus I did some applications in FoxPro in the past but they werent that hard, thats why I think I see the
crossing to .NET easy, I did software for a Pharmacy, 2 more for a money transfer company so I guess they werent
that hard to code, the DB was simple as well and I guess that is the reason why I took this post as simple and I did not
realize that there are people with more deep VFP coding in their applications so I regret if I made myself unclear.

its the time for us to migrate, no doubts, but since I have been out of VFOx for a long time i guess I need to take those
VFP tutorials back to the scene if you know what I mean. When I used Fox I used Fox 2.5 for DOs and the VIsual Fox from
visual Studio 6, so imagine how long it is since I used it, long time ago. when I met Visual Basic, I stay with it but I love fox for
its simplicity to code, but I found it very limited in matters of use with Windows API and related stuff therefore I stayed with VB.

sorry If my comments hurted the VFP users, it was just my opinion ok?