>>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?
>
>That makes sense. < g >
>
>One of the things I like about the VFP .Net Toolkit is that all the source code is provided as well. See a function you like, but you could like it better? Go grab the source and redesign/recreate it to your liking. Tada! StringToFile!

Yes - and that's exactly what I'll be doing with it. BTW - I appreciate the fact that it exists very much for just that reason.

Thanks!