Another Visual Basic question - data fails XML parsing

[DimPrawn]

Get a decent contractor in to sort it all out.

[Moose423956]

Get a decent contractor in to sort it all out.

Good idea. Do you know one?

[DimPrawn]

Good idea. Do you know one?

Not on your rate, no.

[BigRed]

That's an avenue I'm exploring via a REPLACE, but it's up to the client.




I believe this is what it's doing. I'm not a SQL Server expert, but I think the character set is "SQL_Latin1_General_CP1_CI_AS" - at least that's what I get when I run the command

SELECT DATABASEPROPERTYEX('DBName', 'Collation') DatabaseCollation;

Is that a character set?

It is, but collation can be specified down to column level. FWIW SQL_Latin1_General_CP1_CI_AS:- Latin1-General, case-insensitive,
accent-sensitive, kanatype-insensitive, width-insensitive for Unicode
Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data

XML in SQL Server? go use MongoDB, Postgress, nosql and leave us dbas alone

[Moose423956]

Thankfully, the client has agreed to replacing the dodgy characters with valid ones. Even I can manage to code that!

[rsingh]

Can't you set the writer to encode in utf16?