Volatile primary keys (was: A_SAVERECORD won't save :-()

Hello,
today I know more about the problem. :-}

We use Access to update attached Oracle tables. The primary keys for these tables are generated via triggers.

When we try to save a record with the _same_ values as an already existing one (without the primary key of course) Oracle works fine; but Access simply shows #DELETED in every field and says that the record has been deleted by another user. When we look again (e.g. close the table and open it again) the record is there...

This only happen when the new record has the _same_ values as an already existing one... %-(

Anybody have a solution to this problem?

Thanks in advance

        Martin

P.S.: F'up!

In <2DutyASIBh108h_at_dream.hb.north.de> ms_at_dream.hb.north.de (Martin Schroeder) writes:
>Hello,
>I'm having trouble with a form.
 

>In the AfterUpdate event of one field is this piece of code:
 

>----------- snipp -----------
> DoCmd DoMenuItem A_FORMBAR, A_FILE, A_SAVERECORD, , A_MENU_VER20
>
> Query = "Select * from LONG_TERM_SCHEDULE_CALL "
> Query = Query & "WHERE LTS_ID=" & Me![ID] & ";"
 

> Set LONG_TERM_SCHEDULE_CALL = MyDB.OpenRecordset(Query)
>----------- snapp -----------
 

>The problem is that sometimes A_SAVERECORD _doesn't_ save the record
>(but doesn't return any error!) and subsequently Me![ID] is NULL, which
>let's the OpenRecordset fail.
 

>The table is an attached Oracle table via ODBC.
 

>We're using MS-Win3.11, MS-Access 2.0, Oracle 7.1x and the Oracle ODBC
>drivers.
 

>Anybody seen this problem before?
 

>Thanks in advance
> Martin
 

-- 
               Martin Schr"oder, MS_at_Dream.HB.North.DE
The juvenile .sig squirter wanders through the net searching for a
suitable Internet provider to cling to and make it's home for life.
For this task it has an AOL'ers nervous system.  When it find its
spot and gets an account, it doesn't need it's brain any more so it
posts MMF schemes. It's rather like reaching Pearth. (Adam Haberlach)