I think you're looking in the wrong place.

>That is the results of my query, not a piece of the code. It is generating that when I execute my query. It should be generating a bunch of details lines like it does in 2005.
>
>This is the start of the query:
>
>

>Set NOCOUNT ON
>
>Declare	@poscode as varchar(10),
>	@posdesc as varchar(100),
>	@acctno as varchar(20),
>	@provcode as varchar(20),
>	@PatientID as varchar(25),
>	@ChartNumber as varchar(30),
>	@ChartID as varchar(30),
>	@Last_Name as varchar(30),
>	@First_Name as varchar(30),
>	@Middle_Initial as varchar(5),
>	@Sex	as char(1),
>	@DOB as char(10),
>	@SSN as char(11),
>	@ID as varchar(20),
>	@LastName as varchar(30),
>	@FirstName as varchar(30),
>	@MiddleInitial as varchar(5),
>	@Title as varchar(10),
>	@Suffix as varchar(10),
>	@UPIN as varchar(20),
>	@Name as varchar(100),
>	@LocID varchar(20),
>	@DocDateTime as varchar(8),
>	@DocumentName as varchar(80),
>	@OldDocDateTime as varchar(22),
>	@OldSubject as varchar(80),
>	@Filename as varchar(50),
>	@path as varchar(50),			
>	@page as varchar(10),
>	@documentid as varchar(40),
>	@SQL as varchar(8000),
>	@COPYSCRIPT as nvarchar(4000),
>	@CREATEDIRSCRIPT as nvarchar(4000),
>	@DELETEDIRSCRIPT as nvarchar(4000),
>	@Folder as varchar(100),
>	@Export_FileName as varchar(100),
>	@CONVERTSCRIPT as nvarchar(4000),
>	@ProcessedFilename as varchar(50)
>

>>Sorry but I' don't see what the problem is. It's just a piece of commented T-SQL code.
>>
>>>Ah, ok. Found that, but when I run the query I built in 2005, I get this:
>>>
>>>

>>>/*-----------------------------
>>>Set NOCOUNT ON
>>>
>>>Declare	@poscode as varchar(10),
>>>	@posdesc as varchar(100),
>>>-----------------------------*/
>>>

>>>
>>>Any ideas?