Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2009
    Location
    in the web
    Posts
    13

    Unanswered: Controlling Character Conversion During a Session

    Hello,

    sometimes, while executing a query i get this error :
    WARNING! Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?'). (severity 16) in.....
    I'm still searching to figure out why this problem apears only in some cases, i think when the quantity of the received data is more important.
    I read this article :

    SYBASE SQL Server System Administration Guide
    but things's still not clear.
    how to resolve it?

    someone has already encountered this problem?

    thx
    we like difficulties

  2. #2
    Join Date
    Apr 2009
    Location
    in the web
    Posts
    13
    for more information, i'm using php connection, i generate an excel File, that contains the result of the query, the header look like :
    Code:
    session_start();
    header('Content-type: text/html; charset=iso-8859-1');
    and this query
    Code:
    EXEC sp_helpsort
    send :
    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
    which i was enough clear
    we like difficulties

  3. #3
    Join Date
    Nov 2004
    Posts
    1,427
    Provided Answers: 4
    SYBASE SQL Server System Administration Guide
    Are you in the right forum? This is the MS SQL Server forum
    With kind regards . . . . . SQL Server 2000/2005/2012
    Wim

    Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
    Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages

  4. #4
    Join Date
    Apr 2009
    Location
    in the web
    Posts
    13
    Quote Originally Posted by Wim View Post
    Are you in the right forum? This is the MS SQL Server forum
    Yes Wim, i'm in the right forum, i just showed what i have found when i was searching in the web using the key words that i had.
    i think it's about the coding of the tables that changes from table to table, that's why i get this error but only sometimes.
    we like difficulties

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •