Re: access and odbc error with a database link

I have an Access app that's a front-end to an Oracle back-end with triggers on the tables, but have never seen the problems you mention.

Some things to check:
- Oracle permissions on the table, and how you are connecting to the Oracle tables.
- Do the Oracle tables have primary keys? If not, Access won't allow you to insert records. (I don't think it'll stop updates to existing records, though.)

Oracle itself should not care that the data changes are coming in via ODBC.. a trigger will fire if the relevant action is occurring on the table. If you disable the trigger and just try editing the data in the table from Access, does that work? (It may not be a problem with the trigger, but with the connection setup.)

Hope this helps,

Anne Nolan

Bowen wrote:

> Hi-
> Does anyone have experience in successfully getting an Oracle trigger which
> is directly on the underlying Oracle table to fire from access. I get it to
> work out side of access no problem, but as soon as I add the reference to
> the oracle database link. ie: insert into sys.testable_at_Test.cc.university.
> Then I receive an odbc error that it can't update a linked table. If I try
> to update the table directly though access, I get an ORA-02041: client did
> not begin a transaction. I am placing the trigger directly in Oracle
> because the access application is an off the shelf deal, that I don't want
> to mess with because of legal issues.
Received on Fri Feb 08 2002 - 10:38:44 CST