|
Archives of the TeradataForumMessage Posted: Wed, 08 Feb 2006 @ 16:43:00 GMT
Hi All, I'm hoping you can help me with this issue. In one of our applications, end-users have been able to run a Microsoft Access application that connects to a linked Teradata table via ODBC and both delete and update records in the Teradata table from Access. Recently, the user upgraded their Queryman to SQL Assistant and are not running the Teradata ODBC Driver Version 3.02.00.00. I'm running under driver version 3.03.00.05 and neither of our desktops can execute the Delete statement any longer (the error code returned in Access has no associated descriptor: Error -7778). Amazingly, the Insert statements from an Access table still function with no issue. The delete statements that are being executed are simple: Delete ABCD0846.TEMP_TABLE.* from ABCD0846.TEMP_TABLE. In DBC.ACCESSLOG, this statement is being converted to: Delete from ABCD0846.TEMP_TABLE where ColA = ?; ColA represents the column from the table which is also the Primary Index for the table. Apparently, Access is sending individual delete commands to Teradata based on index column values. Has anyone else encountered an issues with ODBC connected applications attempting to do Deletes in Teradata, and if so how were you able to get around these issues (if you encountered these specifically)?
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||