>> Basically it was thought by some that so much would be lost, it would hardly be FoxPro any more. <<

And now it isn't FoxPro any more.

Personally I would have happily let some of the features go away to have it become a .NET component.

I never store data in local DBC/DBF tables - been burned far too many times to do that. The only part of the local data engine I want is the ability to work with cursors which is already in .NET (crappy implementation but it could be done right).

Macro substitution may or may not be a real issue in .NET. Suddenly it looks like it really would not be an issue.

Oh well. Maybe etecnologia can save the day on that.