Thanks for replying so soon, however, after reading the article I miss the conection as to how this solves my problem
My fault possibly for being so vague. I'm am replicating between two SQL2000 servers both running SP3.
So I'm a bit confused as to how the article Q239458 (previously published under Q239458 ) applies to my situation. This article is talking about, "Replication: Problems Mapping Characters to DB2 OLEDB Subscribers." My subscriber is a SQL 2000 Server not DB2.
All columns defined as NOT NULL on the publisher are NOT NULL on the subscriber. All varchar columns on the publisher are varchar on the subscriber. All bit columns on the publisher are the same on the subscriber in fact the two tables are identical.
May be I'm being dense but I don't see the relation between the article and my problem. May be you could elaborate a bit more.
The only other thing I can come up with is that one of the rows has a field that exceeds the limit of the datatype you have choosen. Such as your column is set to a datatype of varchar(100) and one row's field has exceded the 100 character limit. Granted if your using the replication wizard this shouldn't happen but, hey I've seen wierder things.
If I should think of anything else in the next couple of days I will post again.