>On the topic above, can you explain how the VFP runtime files are different than VB runtime files or the .NET CLR "runtime" files from a legal perspective?

The VB 6.0 runtime file (one DLL) was included in pervious Windows operating systems since VB was a general Windows development tool and various components were written in VB and dependent on that one file. The .NET Framework is included in Windows Server 2003 and will be include with Longhorn since more and more components will be built on top of the .NET platform and dependent on those files. There is nothing in Windows dependent on the VFP runtime files.

>Would Microsoft have an issue if the VFP community banded together to make the distribution of basic (per redist.txt) VFP runtime files easier ... along the lines of what Craig Boyd suggested earlier in this thread?

VFP runtime files can only be distributed by a licensed VFP developer in conjunction with a VFP application per the EULA and redsist.txt details. There are wiki docs and other sources online that outline information descriptive information which can be added to by VFP community members if and when needed.