>Another reason is for extensibility, we want our community to be able to improve and perfect the functionality and as you know it is easier to do that in VFP than in other languages, and you really know that, the code in the FFC and XSource would have taken a lot more of effort to write it in another language as C++ or C#.
>
>So if not solution comes implemented in VFP and there is one in other language, we'll use it because we want to speed this as much as possible, but for our community right now the best language for this task is VFP.
What I've been wondering about: How about Rushmore? Or more precisely, how about the typically superb performance when querying? Do you think you'll gonna need the LINQ facilities that are currently implemented? (I'm assuming here that database features in VB.NET will show a similar speed after the LINQ project has finished.)
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
