>>Well, since .NET development takes months and several programmers, I had better stop reading this and get to work!!!
>>
>>Seriously, where did you read that/who did you hear that from?
>>
>>
>It absolutley amazes me that these people can spew out the falsehoods with a straight face. Never used the product, but they're experts in why you can't.

Because people read.... learn from experiences from other people, people who not as biased as some of the other members here. I'd rather listen to guys like RickS and JRyan who do have enough experience in .NET to draw a conclusion. Also as oposed to the pure 'practical guys' some look at the development tool from a higher perspective rather than blindly gain personal experience and jump into the unknown just for the sake of being on the 'cutting edge' (for whatever that means).

You don't have to be einstein to see that .NET lacks the powerfull local database engine and
is strongly typed meaning that some things are harder to do (Run time compilation/evluation of code through macros, execscript, compile, late COM binding).

As JohnR mentions, if you are not concerned about these features, then great, sure you won't miss much when going .NET. If you do, you'll find yourself in a difficult position when transitioning to .NET as there are no real equivalents to those VFP features.

Now since I'm not an expert using .NET, I'd like to ask you how I'd do the following:

USE SomeEmbeddedTableInExe ALIAS MetaData
LOCATE FOR ID = nSomeId
cCommand = MetaData.Command
USE
lRet = EXECSCRIPT(cCommand)