@Douglas:
por mi parte no tengo ninguna experiencia práctica que aportar con respecto a MongoDB, pero fijate en lo que opina Rick Strahl (
http://www.west-wind.com/wwThreads/default_frames.asp?Thread=3CB136FHS&MsgId=3CF1761PE). Por si alguno no lo conoce Rick fué MVP VFP, MVP C#, creó West Wind Connections y hasta es coautor de un libro de VFP:
---
I don't think this will be a good idea. MogoDb is essentially a No Sql solution that maps to objects dynamically. For the .NET providers, you have to provide .NET types in order to make it do the right thing (ie. mapping an object from Mongo to .NET). This means it's really not dynamic and you'd have to create your types up front in .NET for mapping.
Mongo retrieves data as JSON, so possibly you might be able to map data using the Mongo REST/JSON api (or one of the addon front ends). But Fox conversion from JSON will be slow. JSON parsing in FoxPro is unfortunately slow.
Overall i just don't think this is a good match especially if performance is important (which is one of the primary reasons to use Mongo in the first place).
Possible - yes. Practical - probably not.
---
HTH,
Mario