David,
>I have heard these arguments why VFP doesn't fit into .NET for a long time now. There are two things that separate VFP from VB. One is the language that is designed to handle data and the other is the fast data engine. If Fuji can put COBOL in the CLR why can't MSFT put VFP in the CLR? Add the data engine and using the language VFP would not look like VB. Unless they added SEEK (or other commands) to the VB.NET. I don't know.
>snip<
Dunno.. Ask the VFP Development Team.
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
