"Invalid Database Object Reference"

[jgelpi16]

I am attempting to run the below append query. When I run it in Datasheet view it runs just fine. However, when I try to append it throws the error "Invalid Database Object Reference". Can anyone help out or point me in the right direction? I'm at a loss as to where to start. I have ran compact and repair on back-end DB...All is well...

INSERT INTO tblSLAudit_Exceptions ( EXCEPTION_ID, DIVISION, REGION, DISTRICT, STORE, TRANS_DATE, CASHIER, TOTAL_AMOUNT, TOTAL_COUNT, EXCEPTION_TYPE, RESPONSE_TYPE_ID, NO_OF_ASSOC_AFFECTED, COMMENTS, MODIFIED_DATE, CLOSED_DATE, STATUS, DUE_DATE, INSERT_DATE, EMPLOYEE_NUMBER, BASE_STORE, NO_OF_HOURS_IMPACTED, BEGIN_DATE, BEGIN_TIME, REOPEN_DATE, REOPEN_TIME, IS_EDUCATED_ON_REGULATIONS, END_DATE, CASE_VALUE, NUMBER_OF_AFFEC_STORE_MANG, NUMBER_OF_AFFEC_AST_STORE_MANG, NUMBER_OF_AFFEC_CASHIERS, NUMBER_OF_AFFEC_OTHER, IS_STORE_HR_CHANGE_REQUEST_COM, HIST_CURR )
SELECT SLAUDIT_FDT_SA_EXCP_SUMM_HIST.EXCEPTION_ID, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.DIVISION, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.REGION, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.DISTRICT, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.STORE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.TRANS_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.CASHIER, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.TOTAL_AMOUNT, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.TOTAL_COUNT, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.EXCEPTION_TYPE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.RESPONSE_TYPE_ID, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NO_OF_ASSOC_AFFECTED, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.COMMENTS, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.MODIFIED_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.CLOSED_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.STATUS, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.DUE_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.INSERT_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.EMPLOYEE_NUMBER, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.BASE_STORE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NO_OF_HOURS_IMPACTED, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.BEGIN_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.BEGIN_TIME, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.REOPEN_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.REOPEN_TIME, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.IS_EDUCATED_ON_REGULATIONS, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.END_DATE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.CASE_VALUE, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NUMBER_OF_AFFEC_STORE_MANG, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NUMBER_OF_AFFEC_AST_STORE_MANG, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NUMBER_OF_AFFEC_CASHIERS, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.NUMBER_OF_AFFEC_OTHER, SLAUDIT_FDT_SA_EXCP_SUMM_HIST.IS_STORE_HR_CHANGE_REQUEST_COM, "HIST" AS HIST_CURR
FROM SLAUDIT_FDT_SA_EXCP_SUMM_HIST LEFT JOIN tblSLAudit_Exceptions ON SLAUDIT_FDT_SA_EXCP_SUMM_HIST.EXCEPTION_ID = tblSLAudit_Exceptions.EXCEPTION_ID
WHERE (((SLAUDIT_FDT_SA_EXCP_SUMM_HIST.EXCEPTION_TYPE)="HSLC") AND ((tblSLAudit_Exceptions.EXCEPTION_ID) Is Null));

[pkstormy]

Try breaking the query apart, first eliminating expressions. When the query executes after you've deleted an expression or field, then you've pinpointed the problem.

[jgelpi16]

Solution was front-end compact and repair. Thanks for the suggestion.

[pkstormy]

Weird. Thanks for posting the solution. (I worry a little when compacting/repairing fixes a query issue on a frontend).

[jgelpi16]

Weird. Thanks for posting the solution. (I worry a little when compacting/repairing fixes a query issue on a frontend).

Yea...Tell me about it. I've been running into a bunch of corruption issues lately . Forced me to develop some good back-up practices though!