I've been told to migrate one MS-Access 97 database to oracle. Oracle
Migration Workbench did the
trick in an extremely clean, quick and complete way. Tables are created,
populated with data and it is
now when the problem starts. The people that were using this Access
database were doing so
If VB code was connecting to Access db through ODBC datasource, just modify
this this datasource (or delete/create new one with the same name) to use
Oracle ODBC driver (instead of ACCESS ODBC driver) and point them to the
entry in tnsnames, which you create for them to use.
Still, probably they
Check the ODBC configuration in Control Panel and make sure the connection
is not set to read only. If you have primary keys on the tables access
should be capable of seeing these and thus will allow updates to the table.
If not you should be prompted to supply the key columns from a list of
To: Multiple recipients of list ORACLE-L
Subject: RE: MS Access migration to oracle
Either it's the privileges on the tables or
the tables do not have primary keys or unique keys.
Access will put the table in read only mode if it does not
have PK or Unique
key.
Waleed
-Original
It's just not Access developers. I was handed an old Oracle db where less than half of
the 300+ tables have a primary key or unique constraint and no tables have a foreign
key.
Think about it.
Jerry Whittle
-Original Message-
From: Gogala, Mladen [SMTP:[EMAIL PROTECTED]]
