Let's not start an argument, that really was NOT my intention. I wrote the following:

1. Sorry, nothing similar in dotNet. Well, DotNet dos NOT have those four commands, period. What you and I mean with "similar" obviously differs, and that's fine with me. Gerard asked for EXACT replacement for the commands, and there are none in DotNet, at least so far.

2. That's one of many reasons why so many has decided that Visual FoxPro will remain their primary tool for a lot of years to come. This is a fact, period. I do not say that many has not left VFP for DotNet, because many has. I also did not make any comments about why some use VFP and some has shifted to DotNet, because that's simply not a debate I want to be part of. Everybody must make their own decision based on their own specific situation. VFP has it's pros and cons, and DotNet has its pros and cons.

3. DotNet and data crunching, forget it, or use SQL as backend. What I say is if you use DotNet, you must use a separate data engine, like SQL server, unless you have relatively little data. Unless something has changed lately, that's also a true statement. I subscribe to Code Magazine, in which I read all the articles. I have read more than you may believe about DotNet, and what it can do and how it can be done, because I want to know whether it may be smart for me also to shift in the future. But I want to be respected for my wish to make my own decisions, because only I know what's best for my own needs.

Again, my message was NOT ment as a contribution to a DotNet/VFP argument! I tried to be short and concise, but since my english is not perfect, I may have expressed myself less clearly than I intended to.

>
>I will answer your question if you take the time to read what I REALLY wrote in my answer. My answer was 100% correct, but I know you have problems accepting that.
>
>(If I have to rephrase my answer, I will: Since dotNet has no database engine built in, you must use an external database engine, which in practice usually means SQL.)
>
>If you want to insult me, be honest about it, and don't hide behind a cloudy curtain and throw false accusations. This guy asked a question and I gave hime the correct answer. So what's the problem?
>
>
>I didn't make any false accusations...I didn't make any accusations at all. I asked two questions, the answers of which shouldn't be contingent on anything I say.
>
>I read your answer several times before I responded. It was poorly worded and didn't even attempt to seek clarification from a rather generally worded initial question. What you failed to see is that questions from people ascending the .NET learning curve aren't always concise, and require some digging to get to the point. [and that's nothing against the initial question, it often happens]
>
>Tore, you have a good reputation in the VFP world - but that in itself doesn't translate to handling .NET questions that you're neither equipped nor prepared to deal with. Anyone with experience would have sought more details from Gerard....you didn't...quite possibly because you can't.
>
>You stated, 'there's nothing similar in .NET'. If you were referring to ADO.NET, there are equivalent statements and functions. If you were referring to operations against back-end data, then it's comparable to the way you'd call a SQL Server stored proc from a variety of different development tools.
>
>Had you clarified with your rephrase, it would have made things a little different. But as it stands, you were anything but 100 percent correct.
>
>I'm not insulting you at all - I'm telling you that you should hold yourself accountable.
>
>Kevin