>Seems like that would be an ideal case for varchar.

For as long as the backend is SQL Server. That would then force us to adjust that SQL later on as I believe the current syntax is ANSI compiant where a field type with Varchar woudn't.

Also, this makes it invisible in the code to know exactly what is going on unless to go in the database and check the type of field. As, I had to try a lot of combinations on this one and some of them could be really confusing as per the backend configuration.