Quantcast
Channel: Microsoft Dynamics GP
Viewing all articles
Browse latest Browse all 38722

Forum Post: RE: AA Primary Key SQL errors in GP 2015

$
0
0
Hello, thanks for your response. I ran the SELECT's you provided: SELECT * FROM AAG10001 WHERE aaGLWorkHdrID IN (SELECT aaGLWorkHdrID FROM AAG10000 WHERE JRNENTRY NOT IN (SELECT JRNENTRY FROM GL10000)) --Returns 51 rows with 2 unique aaGLWorkHdID SELECT * FROM AAG10002 WHERE aaGLWorkHdrID IN (SELECT aaGLWorkHdrID FROM AAG10000 WHERE JRNENTRY NOT IN (SELECT JRNENTRY FROM GL10000)) --Returns 51 rows with 2 unique aaGLWorkHdID SELECT * FROM AAG10003 WHERE aaGLWorkHdrID IN (SELECT aaGLWorkHdrID FROM AAG10000 WHERE JRNENTRY NOT IN (SELECT JRNENTRY FROM GL10000)) -- Returns 0 rows SELECT * FROM AAG10001 WHERE aaGLWorkHdrID NOT IN (SELECT aaGLWorkHdrID FROM AAG10000) -- Returns 3 rows with 1 unique aaGLWorkHdID SELECT * FROM AAG10002 WHERE aaGLWorkHdrID NOT IN (SELECT aaGLWorkHdrID FROM AAG10000) -- Returns 14 rows with 2 unique aaGLWorkHdID SELECT * FROM AAG10003 WHERE aaGLWorkHdrID NOT IN (SELECT aaGLWorkHdrID FROM AAG10000) -- Returns 18 rows with 1 unique aaGLWorkHdID I have noticed that none of the above tables (AAG10001, AAG10002, AAG10003, AAG10000) are not in the script provided from Microsoft. Do you have a script similar to Microsoft's that you can provide to fix my issue? Thanks!

Viewing all articles
Browse latest Browse all 38722

Trending Articles