This is one of those things you will pick up if you use formatted SQL when submitting data to the database via an ASP page. If you using ADO you won't have this problem but. I like using formatted SQL cause its native to the any database. If its native it will run faster. Any performance gains I can get I'll do it. I haven't did any performance testing between using ADO or formatted SQL but its just my opinion. If you want to view live demos how-to Insert and Update Records using Formatted SQL statements.
Here is a piece of code to get rid of this problem, as your building your SQL string just use the replace statement
Database Code 
/ 6 
ASP.NET Export to Excel and Word using VB.NET and C#
