|
though
it's still worth a try - I don't think you'll be able to do what I've
suggesed....unless the docs on MSDN are wrong. I found two statements
there that lead me to this conclusion:
1. "FOR XML cannot be used in a
selection that requires further processing in a stored
procedure"
2."Generally, FOR XML cannot be used for any
selections that do not produce direct output to the Microsoft® SQL Server(tm) 2000
client."
What's
more, many areas of the SQLXML docs point the developer to the "Executing SQL Statements Using HTTP" section of the site...
which implies that my first hunch was right - FOR XML is really
designed for HTTP access use. That said, the docs don't appear to be
updated for SP3, so they may not be applicable when running SP3. Don't
know - I haven't had time to test SP3 yet. Sorry.
~Simon
Simon Horwith
|
Title: Message
- [cf-xml] CF5, SQL Server 2K Question Brian LeGros
- RE: [cf-xml] CF5, SQL Server 2K Question Simon Horwith
- Re: [cf-xml] CF5, SQL Server 2K Question Brian LeGros
- RE: [cf-xml] CF5, SQL Server 2K Question Simon Horwith
- Re: [cf-xml] CF5, SQL Server 2K Question Brian LeGros
- Re: [cf-xml] CF5, SQL Server 2K Question Simon Horwith
- Re: [cf-xml] CF5, SQL Server 2K Question Brian LeGros
- RE: [cf-xml] CF5, SQL Server 2K Question Lomvardias, Christopher
- RE: [cf-xml] CF5, SQL Server 2K Question Askew, Jason
