Let's agree to disagree, then.

>IMO, if you're having that problem, it's the fault of the developer...not Microsoft. The developer should buffer and validate data in such a way that bad data doesn't get in. And the same holds true for SQL Server, Oracle, MySQL, etc.
>
>>That may well be true about BROWSE. My point remains the same, though: is that the user's fault or the vendor's? To me the answer is clear, and that isn't Microsoft-bashing. I would say the same of, I don't know, Intuit, if a special character typed into an amount field corrupted your financial data file.