Gary,

They're talking about the data mechanisms which is what keeps a lot of us using VFP. The VFP IDE, UI and command syntax isn't that special and easily could be sacrificed IMHO. Heck, many of us have been writing HTML and dHTML frontends for years, bypassing the VFP UI completely. Some of that has been transferred to ASP.NET without a hitch.

Its just like what would do with any piece of T-SQL and database/tables except that its "local" and it will interact easily with a "daddy" SQL server :)

I routinely create quite large VFP cursors, index them (saves about a second per transaction) then recreate the cursor for the next transaction. I'm not convinced I can do that as well using a local db via ADO.NET or rudimentary T-SQL. I'm looking forward to Linq. At least I hope I am ;-)

Personally, I am getting messages all the time from VFP developers who are starting to look over to the dark side :) I don't think the fear is there anymore

Starting? I think *most* people have looked and listened to a level they regard as sufficient to make a decision. Who can name a real-life VFP luddite who refuses to learn anything about dotNET or to consider whether staying with VFP is a viable option today, next year or in ten years? Some stay; some go; some boast they've gone but seem unable to stay away. I don't see fear, I do see wagon-circling in the face of war whoops and deliberate provocation from certain quarters.

Anyway, SS Compact is a useful initiative. Lets hope the sloganeers don't persuade MS to add every imaginable facility and bloat it up. ;-)