I've been writing about it over and over again here on the UT as I did in that thread and it's frustrating to see the same questions over and over again. This goes back to my original point that this basic stuff should be in the VFP docs. My website and ActiveVFP are the result of years of work on this subject - this has been my way to show developers how to do it, with a demo, documentation, and open Source software. An article or session here and there will help some developers, but, to reach the most the basic stuff should be in the docs...
>>
>>As for your question above... I suggest that you consider doing as others have done over the years when putting developer tools to use in practical ways... write about it. If you would advise creating a VFP MTDLL to preserve investment in code, why not show others HOW to do that and WHY by just writing a simple article or whitepaper, either for publication or to post on your website? You might find that once you get started on it, that the ideas will just flow easily, and I would be happy to help edit it for you if you want.
>>