Thanks for clearing that up. I actually did read the beginning of the thread, but I guess I mis-read it. Someone had posted a link to a list of things that are changing (broken to some) in the next VB, and said that they hoped there wasn't a similar list for the next version of VFP. I guess I implied that Craig's two items were definite changes, not what would change if VFP went to the CLR.

>Jonathan,
>
>>Maybe I've missed something, ...
>
>You just missed the beginning of the thread, where the context of the discussion was about what Foxpro would lose IF it were ported to the Common Language Runtime (CLR) of .NET.
>
>That is NOT happening, so don't panic! :-)
>
>>...is there any documentation or other discussion areas on this? Sorry for so many questions, but this is the first I've heard of any of this.
>
>http://fox.wikis.com/wc.dll?Wiki~ShouldVFPBeInTheCLR
>http://fox.wikis.com/wc.dll?Wiki~ShouldVFPBeInVSDotNet