>>Call me thick or something, but I just don't understand this mindset. Regardless of it's origin, isn't an additional set of functions a good thing to add to your toolbox? For example, the StrToFile function in the VFP .Net Toolkit takes a string and writes it to a text file, just like it does in VFP. What's the difference behind calling that function INSTEAD of executing the C#/VB.NET code behind it.
>
>Perhaps you missed the point. I stated clearly that I'm all for well wrapped fucntionality. So if you're talking about that functionality of StrToFile - fine - but why do I need to be tied to the VFP syntax? What if I like StringToFile() instead? What if I want to pass my parameters in a different order. Frankly, I think many VFP functions ask for the parameters in illogical order anyway. Why would I want to perpetuate that and/or limit myself to the VFP syntax?
>
>Thanks,

Hi Kenn.
For me VFP .Net Toolkit is very good idea. Why reinventing the wheel ?
For me would be more simple to start with something that I know. I want to start quickly not in an ideal new way. Maybe if I had enough time...
I am very glad that someone in this world had had enough time :)