Hey Mike!

We're tracking it down - sort of. If we put a constant in there, it works as expected. If we use an expression, the expression evaluates to the number we expect (in this case, 1) prior to the call, but we see the issue. If we store the result of the calculation in a variable and use the variable in the call, it works as expected. Again, only for this one client. Very strange, but our work-around is to store the result in a variable and use that in the call to CursorToXML(). No performance penalty and the problem goes away.

thanks for your response,
Mike,