Re: Oracle performance decrease using Access7

This means that Access can't identify a uniquely indexed field to use as the Primary Key for updates to the table. It's asking you to do so on it's behalf. In this situation, with no primary key, Access' RecordSets will be extremely inefficient because it has no way to form a primary key other than using the contents of every field in the row. This is why your performance was so bad.

With a primary key, Access can request the rows using a short, small list of primary keys. Without seeing your actual table definition, I can't tell you why Access is asking for this information, though.

Troy Perchotte wrote:
>
> Thanks John and Kevin,
>
> This is strange. On one of the many times that I've been attaching to the Oracle
> tables from Access, I ignored the question that Access displays (and was giving
> immediate results):
>
> "To ensure data integrity and to update records, you must choose a field or fields
> that uniqely identify each record. Select up to 10 fields"
>
> On all previous attachments, I've been selecting the "CustID" field as the field
> that identifies the uniqeness for this table. Now even the 106 column table with
> 13'000 records displays within an acceptable 2 seconds.
>
> Is there any reason why I would need to select any field for the Access question
> ("...you must choose a field or fields...")?
>
> Troy Perchotte
Received on Wed Apr 15 1998 - 15:28:54 CDT