Linked SQL tables and dbSeeChanges?

[Jefferson Berlin]

Hi. I've just upsized an Access 97 app to Access 2002 and
moved the data to SQL Server 2000. The SQL tables are
linked in the Access app (this is not an ADP) and there's
a form that is bound to a query based on two of the linked
tables. When I make a change to a record in the form, the
change is saved correctly, but I get the error "You must
use dbSeeChanges option with OpenRecordset when accessing
a SQL Server table that has an IDENTITY column."

For starters, neither of the tables in the query contain a
field defined as an IDENTITY field, though they each have
a key field. But more importantly, does this mean I can't
use bound forms when the data is in SQL Server? Do I have
to base everything on ADO or OLEDB recordsets? How do I do
this?

Many thanks for any help you can offer.

Regards,
Jefferson

 

[Van T. Dinh]

Do you have a PrimaryKey defined in the Table?

Also, when you upsized the Tables into MS-SQL2K, did you select to include
the "upsize_ts" (Upsize TimeStamp) Field. I haven't experience this (since
I always include the "upsize_ts" Field) but there are a few problems with
edit if you don't have the "upsize_ts" Field.

 

[Jefferson Berlin]

There is a primary key defined in both tables involved,
and there's an "upsize_ts" field in each one as well. I
also tried creating a view in SQL Server and linking that
from the Access application, with the same result.

I read that linking views would avoid edit problems on
bound forms, but no such luck. Any other ideas you have
would be appreciated.

Thanks for your query.

Jefferson