>AFAIK SQL server odbc driver doesn't support sql_variant type and return the >data as a BLOB. The 'incorrect' data you're seeing is unicode data. You might >check the value and if it has chr(0) in it then convert with strconv(). If you >check client machines probably you would see some of them have unicode support >enabled and some are not.
>
>IMHO using sql_variant in the first place is asking for trouble.
Hi Cetin,
Thanks for the advice, the "sql_variant" field seemed to be a handy feature of SQL Server at the time but I'll look to an alternative.
Thanks again,
Ben
Ben Sugden
"Remember to enjoy hunting - and that means relishing the search for the product that has never been advertised or placed handily at the front of the shop; Life begins on the uppermost shelf, avoid guide books and top 10's like the plague." - Ramsey Dukes
