zimmer9
asked on
I am having an issue with a SQL Statement WHERE Clause in SQL Server 2008, I get the message "incorrect syntax near '=' ?
I am using SQL Server 2008 and I suspect I need to replace part of my SQL Statement WHERE clause:
WHERE StopVoidPay.userid = tbl_CSL_users.msidOld))= False))
with
WHERE StopVoidPay.userid != tbl_CSL_users.msidOld))
but I get confused with the placement of opening and closing parenthesis as follows:
SELECT
bank.entity,
tbl_CSL_StopVoidPay.bank,
tbl_CSL_StopVoidPay.userid ,
tbl_CSL_StopVoidPay.dtCrea ted,
tbl_CSL_StopVoidPay.chkNum ,
tbl_CSL_StopVoidPay.branch ,
tbl_CSL_StopVoidPay.chkDt,
tbl_CSL_StopVoidPay.accoun tNum,
tbl_CSL_StopVoidPay.amount ,
tbl_CSL_StopVoidPay.typeSV
FROM tbl_CSL_bank INNER JOIN tbl_CSL_StopVoidPay ON tbl_CSL_bank.bankID = tbl_CSL_StopVoidPay.bank
WHERE (((tbl_CSL_StopVoidPay.typ eSV)='S') AND
((Exists (SELECT msidOld
FROM tbl_CSL_users
WHERE StopVoidPay.userid = tbl_CSL_users.msidOld))= False)) <---- Line 16
ORDER BY StopVoidPay.chkNum;
Msg 102, Level 15, State 1, Line 16
Incorrect syntax near '='.
Do you know how I can resolve this?
WHERE StopVoidPay.userid = tbl_CSL_users.msidOld))= False))
with
WHERE StopVoidPay.userid != tbl_CSL_users.msidOld))
but I get confused with the placement of opening and closing parenthesis as follows:
SELECT
bank.entity,
tbl_CSL_StopVoidPay.bank,
tbl_CSL_StopVoidPay.userid
tbl_CSL_StopVoidPay.dtCrea
tbl_CSL_StopVoidPay.chkNum
tbl_CSL_StopVoidPay.branch
tbl_CSL_StopVoidPay.chkDt,
tbl_CSL_StopVoidPay.accoun
tbl_CSL_StopVoidPay.amount
tbl_CSL_StopVoidPay.typeSV
FROM tbl_CSL_bank INNER JOIN tbl_CSL_StopVoidPay ON tbl_CSL_bank.bankID = tbl_CSL_StopVoidPay.bank
WHERE (((tbl_CSL_StopVoidPay.typ
((Exists (SELECT msidOld
FROM tbl_CSL_users
WHERE StopVoidPay.userid = tbl_CSL_users.msidOld))= False)) <---- Line 16
ORDER BY StopVoidPay.chkNum;
Msg 102, Level 15, State 1, Line 16
Incorrect syntax near '='.
Do you know how I can resolve this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.