>I think the VFP toolbox is both a proof of concept and an aid to those Fox developers who wish to migrate to .NET. It should also be of help to non-Fox developers going to .NET.
>
>My adivice is to look at the toolkit, not for what it is, but for the idea it represents. i.e., don't scoff at the toolbox for the way it is out of the box. Rather, use it, customize it and in the tradition of Fox, make it your own by tailoring it to your needs...
>
>
>
>>EXACTLY! And If I don't like the parameters or the order, then I can change that - and if I want to change or enhance functionality - then I can do that - and if I don't need all the functions - then I can take some out - and if I need some others then I can add them - and - wow - I'm not using the "VFP toolbox" anymore! ;-)

Yes - exactly again - and that's what I've said I would do and will do. I think it has great value for that and have stated so several times now. I just have little interest in having exact "clones" of VFP functions in my C# apps.