Dragon,

I knew what you were saying but thought I would do a lookup in word just to be sure. It seem like Microsoft is obsessing over .Net to the neglect of everything else. I hate to be negative, but it would be nice to have know problems fixed in Visual FoxPro via a service pack rather that buying a new version of the app to recieve the corrections.

On the possitive side, as long as Microsoft is obessing with .Net, why not use that as an leverage to get some things for Visual FoxPro. I would like to see .Net natively support Visual FoxPro tables. This would fill a huge gap in Microsoft .Net strategy. Currently everyone using .Net need ole db or odbc to get at the data, whether it access, VFP, of MSSQL. This is much more ackward than Visual FoxPro's method of clicking on an [Open] menu and navigating to the target database. Once opened, the table can be browsed and the user is bound into the table. If someone on the network makes an update to a table, it is automatically reflected in the user's browser without the need to click any update, send, of refresh button as is necessary in a async stateless environment. Any updates to the table are immediately passed to the table. This would allow the desktop user to develope apps using .Net with Visual FoxPro tables which would be much easier and less expensive that using MSSQL. This would bring .Net data handling to the ordinary user who is somewhere between Access capable and MSSQL capable. It would allow users of C#, C++, and VB.Net the same ease to databases that is currently available to Visual FoxPro. It would also allow user to deveope app using C#, VB.Net, and C++ Net, and distribute them to consumer where MSSQL is overkill.

What do you think about it? Would extending .Net to include native Visual FoxPro file share handling be a good thing. I was over in the wish list trying to figure out how to make a new entry, when I received word of your post. I'm going to give this more though and I may put it in the wish list. Boy, that wish list is kind of hard to work with.

LelandJ