Re: Oracle 8 ODBC problem with Access

Access need a key to recognize the row that you are updating, if you don't have one key, Access uses the entire row (all columns) to construct one, then if you have a null column Access can't identify it.

Construct a primary key to the table.

Andrew Abrams > escribió en mensaje
<6umpft$qlg$1_at_holly.prod.itd.earthlink.net>...
>I am using Oracle 8 Server, and MS Access 97 as a front end. Lets take an
>example that looks like this
>Table: XXX
>Fname varchar2(20)
>lname varchar2(20)
>*** No Keys
>in access if I am in table view and insert a record lets say the data looks
>like this:
>(Andrew, Abrams) I can insert the record and in turn move off the record,
>move back on to the record and modify either field.
>The problem is when I leave a field blank, consider the following data:
>(Andrew,) [A first name with no last name]. I can enter the data, move off
>the record, and when coming back to update I get an error to the effect
that
>another user is currently modifying the record. I can use SQL worksheet
and
>update that way, but not from Access. What gives?
>
Received on Mon Sep 28 1998 - 04:15:09 CDT