Access97 Data to SQL

[Dianne]

I have an Access 97 program that for many years linked to tables in another
database through drive letter access. Recently, because of speed, we
converted the Access tables to a SQL Server 2000 database and linked the
tables via an ODBC connection.

The program can read the tables but there are several problems. The append
queries that are trying to build new records in one of the SQL tables keep
giving a key violation error. Also, a few of the screens used to append
records to some of the tables no longer let me add records. It will show the
records that were originally imported, and let me delete them, but not add.

The first time I converted, many of the Access queries wouldn't work and we
discovered that in the conversion, the Autonumbering in many of the tables
got lost. Since then, I have set the Identity to Yes and when viewing the
design of the ODBC tables through Access, they are now showing as Autonumber.

Is there some incompatibility between Access 97 and SQL server 2000, or do I
have the wrong data types in the SQL tables? Is there something wrong with
the way I set up Autonumbering in SQL? When the data was all in Access, I
had no problem appending records, but now that the data is in SQL..... what
am I missing?

Please help!

Thanks,

Dianne

 

[Pat Hartman]

Access requires linked ODBC tables to have primary keys or unique indexes or
it will not allow the table to be updated.

Did you upsize the tables originally. I haven't had any trouble when I have
created the SQL tables that way. Just make sure that your tables are
"clean" before you upsize. Make sure all tables have primary keys. Create
necessary indexes. Remove extraneous indexes. Clean up relationships
window. Enforce RI between ALL related tables. Specify Cascade Delete as
necessary.
When you upsize the tables, choose the option to use declarative RI rather
than triggers.

 

[Dianne]

Thank you! That did the trick!

Access requires linked ODBC tables to have primary keys or unique indexes or
it will not allow the table to be updated.

Did you upsize the tables originally. I haven't had any trouble when I have
created the SQL tables that way. Just make sure that your tables are
"clean" before you upsize. Make sure all tables have primary keys. Create
necessary indexes. Remove extraneous indexes. Clean up relationships
window. Enforce RI between ALL related tables. Specify Cascade Delete as
necessary.
When you upsize the tables, choose the option to use declarative RI rather
than triggers.