[TCP/IP Sockets]ConnectionCheckForData()) Error

Error was returned when we compiled a proc. The proc compiles under SP3a.
We're using Standard Edition SP4.
The offending statement is a sub-select in a where clause that uses a union:
and mv.INSTR_ID in
(
select @.INSTR_ID
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)change to:
( select @.INSTR_ID AS [ID]
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
> Error was returned when we compiled a proc. The proc compiles under SP3a.
> We're using Standard Edition SP4.
> The offending statement is a sub-select in a where clause that uses a
> union:
> and mv.INSTR_ID in
> (
> select @.INSTR_ID
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
>|||Hi oj,
Unfortunately, the error still occurs. To compile the proc, we created a
pseudo-talbe from the sub-select with the union statement and joined it
directly to the other tables. FYI, I opened a case with MS.
--
Dave
"oj" wrote:

> change to:
> ( select @.INSTR_ID AS [ID]
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
> --
> -oj
>
> "davidhg" <davidhg@.discussions.microsoft.com> wrote in message
> news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
>
>|||Okay. Without seeing the *whole* thing I'm not sure what would be the case.
The syntax looks right to me.
Do post back if you hear anything.
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:21FFCFE8-EED9-47FA-821C-AE224C630FDC@.microsoft.com...[vbcol=seagreen]
> Hi oj,
> Unfortunately, the error still occurs. To compile the proc, we created a
> pseudo-talbe from the sub-select with the union statement and joined it
> directly to the other tables. FYI, I opened a case with MS.
> --
> Dave
>
> "oj" wrote:
>