By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,657 Members | 774 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,657 IT Pros & Developers. It's quick & easy.

Linking Oracle tables to Access 2K

P: n/a
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?
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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:
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?


Nov 12 '05 #2

P: n/a
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" <ph***********@bellsouth.com> wrote in message
news:b9**************************@posting.google.c om...
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?

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.