>>>I might have worked without the outputs as well.
>>>
>>>>>I will admit that I am a lot more familiar with Sql Anywhere then Sql Server but I would call the sp this way
>>>>>=mySQLExec("execute dbo.siriussp_rsGetBlocks @TemplateID = ?m.nTemplateID,?@nBlockCount, ?@nSeatsCount , 'rsTSBlocks'",program())
>>>>>
>>>>>Seems to me that if you pass a variable by reference then the value would be returned by the SP. I thought "output" was part of the parameter statement of the SP. Anyway, the above is how I would do this is Sql Anywhere.
>>>>>
>>>>This worked. Strange, but my original way (using named parameters) worked fine in one DB and didn't work in another. I tested it right now in working DB and after I made all parameters to be non-named, it worked.
>>
>>Do you mean the original code but without using OUTPUT keyword?
>
>Yes. It seems to me the OUTPUT keyword should only be the SP, but as I said, I have not used Sql Server that much.
>
>>
>>BTW, I made a manual UT refresh and got your message. Prior to that I was not getting any new messages.

I also found what was different (as I today got another problem). For not working database I was using SQL Server Native Client (10). For working database I was using generic (older) SQL Server driver. Using SQL Server driver solved this problem (although I already changed code, so I will not change it back) and another problem with images I had today.