Connecting Tech Pros Worldwide Forums | Help | Site Map

Linking Oracle tables to Access 2K

Phil S
Guest
 
Posts: n/a
#1: Nov 12 '05
I used the Migration Workbench for Oracle 9.2 Client to migrate the
tables in an Access 2K back-end database to Oracle. (The Migration
Workbench is intended to automate the process of migrating tables from
Access to Oracle.) Following the migration, when I try to link the
Oracle table to the Access front-end using Oracle ODBC Driver, I have
to either select one or more fields in the Oracle table as key fields
or not have any key fields. If I select one or more key fields, then
open the Oracle table, all the cells display "#Deleted", but the
number of rows displayed is correct and I can add a row to the table.
If I decline to identify key fields when linking, the data in all the
cells displays correctly, but now the table is read-only.

Thoughts?

Anne Nolan
Guest
 
Posts: n/a
#2: Nov 12 '05

re: Linking Oracle tables to Access 2K


It sounds like you need to go into Oracle and create a primary key on each
table (or at least a unique key). Then relink the tables.

Anne

Phil S wrote:
[color=blue]
> I used the Migration Workbench for Oracle 9.2 Client to migrate the
> tables in an Access 2K back-end database to Oracle. (The Migration
> Workbench is intended to automate the process of migrating tables from
> Access to Oracle.) Following the migration, when I try to link the
> Oracle table to the Access front-end using Oracle ODBC Driver, I have
> to either select one or more fields in the Oracle table as key fields
> or not have any key fields. If I select one or more key fields, then
> open the Oracle table, all the cells display "#Deleted", but the
> number of rows displayed is correct and I can add a row to the table.
> If I decline to identify key fields when linking, the data in all the
> cells displays correctly, but now the table is read-only.
>
> Thoughts?[/color]

A_Rodrigues
Guest
 
Posts: n/a
#3: Nov 12 '05

re: Linking Oracle tables to Access 2K


Indeed, on the Oracle side you must define a primary key. Then rebuild the
ODBC link. You won't be asket to name unique fields and access will not be
read only.

"Deleted" may appear again but meaning that new or edited record have moved
to their postion according to primary key.
Regards
A_Rodriues
"Phil S" <phil.sheridan@bellsouth.com> wrote in message
news:b95327fa.0311050734.78ffeb74@posting.google.c om...[color=blue]
> I used the Migration Workbench for Oracle 9.2 Client to migrate the
> tables in an Access 2K back-end database to Oracle. (The Migration
> Workbench is intended to automate the process of migrating tables from
> Access to Oracle.) Following the migration, when I try to link the
> Oracle table to the Access front-end using Oracle ODBC Driver, I have
> to either select one or more fields in the Oracle table as key fields
> or not have any key fields. If I select one or more key fields, then
> open the Oracle table, all the cells display "#Deleted", but the
> number of rows displayed is correct and I can add a row to the table.
> If I decline to identify key fields when linking, the data in all the
> cells displays correctly, but now the table is read-only.
>
> Thoughts?[/color]


Closed Thread