Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Write Conflict in Access

Write Conflict in Access

From: Bas Haenraets <bhaenraets_at_ortec.nl>
Date: 29 May 1998 18:00:21 GMT
Message-ID: <2465A05A033BD111969500805F4BEF5B0AA0CC@SULACO>


Hi Abdullah,

I had the same problem using delphi and access, and my only solution is to post/commit after each edited field, and then put the table in edit mode again.

Hope this helps,
Bas

> -----Original Message-----
> From: Abdullah Bushnaq [SMTP:dbase_at_raex.com]
> Posted At: Wednesday, May 27, 1998 1:53 PM
> Posted To: misc
> Conversation: Write Conflict in Access
> Subject: Write Conflict in Access
>
> Hi,
>
> We are running Personal Oracle 8 Under NT SERVER 4.0.
> We are using Access 97 to setup the forms, so the tables are all
> linked
> through ODBC to our Oracle Dbase. I have a table that has a primary
> key
> of type VARCHAR2. After creating the table in Oracle, I used Access
> to
> enter the data. Right now the problem is modifying the data, Access
> aboslutely doesn't like it. I get the following error:
>
> =======
> [Write Conflict]
> This record has been changed by another user since you started editing
> it. If you save the record, you will overwrite the chagnes the other
> user made.
>
> Copying the changes to the clipboard will let you look at the values
> the
> other user entered, and then paste your changes back in if you decide
> to
> make changes.
>
> [Save Record] [Copy to Clipboard] [Drop Changes]
> =======
>
> Now, the Save Record is grayed out, so I can't commit the changes.
> And
> needless to say, nobody else is accessing the record, not even the
> table
> or the database. I can add rows, but I cannot modify them, and I just
> noticed that I can't delete them either.
>
> Is this one of the screwy sides of Access? or am I causing an error
> somewhere. On the oracle side I can change the data without problems.
>
> The primary key field is unique and doesn't allow nulls, while the
> other
> fields are not unique and do allow null values. The other fields are
> either VARCHAR2 or NUMBER.
>
> Any ideas would be appreciated,
>
> Abdullah Bushnaq
> [fed up with all the MS Access problems]
Received on Fri May 29 1998 - 13:00:21 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US