Hi,

I have created under Oracle 9i a table RIVERS containing fields RIVER and
DESCRIPTION. RIVER is used as primary key.

In order to avoid that a user could enter in the table two rivers with the
same name but written with a different case (Oracle is case sensitive) I've
created another index based on Upper(RIVER).

When I link the table to Access 2000 manually, the Access assistant asks me
for a unique identifier in table RIVERS. It is rather strange, as a primary
key is already defined in the table under Oracle. But it seems that the
presence of another index based on the same field provokes a conflict ???

When I link the same table with VBA, I'm not asked for a unique identifier,
but then my attached table is not modifiable, it is Read-Only.

Somebody has a solution?

The same behaviour doesn't occur when I do exactly the same thing with
PostGreSQL, which is also case sensitive. The attached table in Access works
perfectly and is modifable...