>We have a client who's setup processed the entire rest of the table, even though nRecords is set to 1. Doesn't happen for us with the same code. Anyone heard of this? Is it an XML parser issue?

Is the 1 a hard coded or constant value? I use that parameter on CursorToXml() alot and haven't seen it fail like you describe.