I'm encountering a totally bizarre error using DBI and DBD::ODBC. I'm using it to connect to a .mdb access database located on a network drive. The terrible thing about the error is that it isn't consistant, and makes absolutely no sense. It occurs on an $sth->execute line, and seems to suggest that the query simply failed:
DBD::ODBC::st execute failed: [Microsoft][ODBC Microsoft Access Driver
+] The sear
ch key was not found in any record. (SQL-HY000)(DBD: st_execute/SQLExe
1) at Batch.pm line 272.
However, I don't understand why it wouldn't just return 0 records instead of throwing a fatal error.
I'm not sure it affects anything, but here is the query:
SELECT ITE_BILL.COMPONENT AS item_type
,ITE_BILL.COMP_DESC AS description
,ITE_BILL.QUANTITY AS qty
,ITE_BILL.PARENT AS parent_id
,ITE_BILL.DRWG AS dwg_num
WHERE (PARENT='7531MD6010B' OR PARENT='7461RD1001' OR PARENT='753