In VFP its a breeze. I am dissappointed so far with trying to understand how to do in .NET but I am going to get on top of it. I have started a set of web pages at my site dedicated to figuring out how do this in .net and describing it in easy terms (just started last nite). I am also going to deal with folder(hard disk) issues that .net may present, project orgnanization taking into consideration multiple project/multiple customer issues. Any other issues I uncover. VFP has a couple but not bad.

Once you become comfortable with it you will often find it useful to put a layer between yourself and other things. Once you learn the language constructs for subclassing you will learn how to override methods and in some cases make use of the parent method but maybe differently.

Like I said below the interface to the parent needs to stay the same though.

3D programming.


>Hi Ron,
>
>great idea! Of course if you've done it ...
>
>Hank
>
>>Cathy, You might consider putting a section on the http://gotdotnet.com/team/vfp/
>>pages desccribing how to install the Tools into a common (common to all projects) tools area, then subclass the VFPTools DLL into a new DLL. Then use that DLL in all projects. As you know this way #1 you can extend/change the tools in the subclassed library. #2, drop new versions down ontop of the old and not loose user specific changes (hoepfully the contract on the interface is pretty firm with the VFPTool developers :~) ).
>>
>>I see that you ask the question of how do you use. I would think that once understood this would be the most preferred method of usage.
>>
>>Ron
>>

What ben makes tracks for what wil be. Words in the air pirnt foot steps on the groun for us to put our feet in to.

Riddley Walker