>>I would not use C# for database applications for the same reasons I would not use C++.
>
>And what are those reasons?
>

Because there are better suited languages such as VB and VFP...


>
I think once you examine the reasons more you will see they don't apply as well to C# as they did to C++... could be wrong.
<

This is interesting wording. Are you saying that the reasoning I am applying to C++ does not apply to C#? If so, why didn't you just say that? The big confusion rests with the last three words "could be wrong". I am not sure what the purpose of those additional words is.

<<
In either case, you have to remember C# has the same frame work as VB.NET, same runtime as VB.NET, same IDE as VB.NET. The difference being you hit the semi colon more regularly, you have to spell things right, and instead of typing out "END FUNCTION" you hit "}". And you never have to see "Dim" *g*
<<

VB has a richer sent of functions. And, FWIW, I like the declarative nature of the language...

>>Second, I don't like the syntax idiosyncracies (sp??) of C#. Now that is simply a preference on my part.
>
>Understood. Hopefully, you will take your own advice and not use this as a reason to create a rule on what place each langauge belongs, which is what we're talking about. Unless there is a specific difference that puts C# at a specific disadvantage, which we have both admitted to not being aware of any.
>

Why do you think I COUCHED IT AS A PREFERENCE??????????? I have not justified my choice on technical reasons? Why? Because technical reasons don't exist one way or the other in this context.

>
Yes, it was a light hearted comment with the intent of invalidating your claim.
>

You did not accomplish your goal...


>>Second, the marathon racer who finished dead last "successfully completed" the race in spite of the fact that the runner did not win.
>
>Fortunately, I'm not racing anyone.

No, but the metaphor applies...


We are done...