>For all I know (and someone correct me if what I know is wrong), VFP going CLR could even force it to give up its local database.

Not could, would. And many other aspects of VFP along with it. Data access in CLR languages is ADO+. Remind yourself of how much of VFP is based on dbfs? That's right, everything. VFP's amazing string manipulation is even internally inextricably tied to the cursor engine, and that would go too.


> Like Ricardo says, somethings we'll need to think about.

I've thought about it, and even though they're offering, we don't want it.