Hi Jay,

I just replied it to you because you said that there was no other Forum/Category where this was/could be posted, and I just wanted to let you and the others in this thread know that there was another thread in the .Net forum with the same subject.

As for converting, since I started my own company, a lot of projects that I have been involved in, where 'convertion projects.' And the main reason to convert was to 'be as productive as possible, by using the best toolset available'.

And I know personally what the best toolset is for me at this time, but I also know that I should try to improve my toolset, even if that means that I need to use another development language. But I don't think my toolset will get any better in the near feature if I had to move away from VFP.


>Ahhh... Ok, I'm still on the bubble with this one though. He does say it's about, "Visual FoxPro Conversion," which is technically valid for this forum, but I also see the point that others are making. I guess it's more about them just not liking the conversion part. Got to say though, probably a third of my contracts in the last 6 years have been exactly that. Converting Foxpro apps/data to some other language/platform. As a Foxpro developer, and not on the .NET bandwagon yet, I don't mind seeing it posted here. I guess I'm the minority though.

Regards,