I have 2 identically configure SQL 2005 servers running the same version, patch level and collation (SQL_Latin1_General_CP850_CI_AS) and transactional replication is set up between the two with basic default article publication settings and table schemas are identical. Where I'm encountering an issue, users must be cutting and pasting extended ascii characters like char(255) to represent an empty string into a non-null required notes column. The transaction replicates to the subscriber, but during the process, replication converts the char(255) value to char(152) ( 'y' with 2 dots above it) on the subscriber and then replication validation check throws an error because the records are no longer the same.
Where in the process is SQL converting this CHAR(255) character to CHAR(152)? Is there an easy fix to keep these tables in sync with extended ascii characters being passed?