JVP

From an app stand point, Fox cannot come close to the security architecture present in .NET...
Sure..you could probably cobble together a solution...but given that the state of the art has progressed a bit since 1995 - it would pale in comparision to what other environments could faciliate.

Gosh, that sounds really ominous. I'm assuming you are talking about Fox the development tool this time, not fox as a catch-all label for local files and tables?

If so, I'm sure this is of interest to everybody here. Can you provide some specifics- not carefully selected minority examples that rely on error or poor design to highlight perceived theoretical disadvantages of either environment, but real-life scenarios that we all might meet where use of dotNET's security architecture would transform security? I.e. help us reach the same conclusion as you rather than just supplying a conclusion that is certainly derogatory about Fox but hardly self-explanatory.

If you were only talking about RVs without the CONNSTRING clause in fat client apps, for example, I'd agree with you, but would like a chance to remind others that CONNSTRING is fantastic for security; that would be much more fun than a somewhat mysterious slam that the whole thing is obsolete and insecure in 2004, which is what your comments seem to imply.