August 14, 2003 at 9:31 am
Our databases are currently on the default 1252 character set, but we deal with clients who do not want to receive any special characters other than the regular US english chars. but could still transmit those special characters to us. So we need to find a way to be able to receive them and filter any special characters out before transmitting them back to the clients or the web. What would be the best workaround in this scenario ?
Also we are currently taking care of this problem by creating CHECK constraints on the name fields to check for any special characters. But this requires creating separate constraints for each letter in the varchar name fields which is like 50 + constraints. Is there any other better way to do this ?
Thanks
August 14, 2003 at 1:04 pm
Sounds to me like you need to do a replacement of the data when you display it. IE: When you have an e with an accent you change it to an e. You can then create a UDF to do the replacement based on character values stored in a table. That way the data in the table is displayed the way you want it. The only problem with that is that if your user needs to modify the data you will lose the original data that you started with.
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed in this post are my own and may not reflect that of my employer.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply