Hi all,

We have a computer system in place which is built using a compiled
front end (not sure what language it has been written in) which reads
and writes data to an Access database. I have done a test migration of
the system to our SQL server and linked all tables back to the Access
database. The problem is that when I execute the front end, I get an
error saying.

You must use the dbSeeChanges option with OpenRecordset when accessing
a SQL Server table which has an IDENTITY column.

Has anyone any idea of a workaround to this as the system is quite old
and not really formally supported anymore.

Is there any workaround for this?

Thanks

Simon

It's a change that needs to be made to the code in the front-end
application, Simon. I'm afraid I don't think there's anything you can do to
fix it if you don't have the source code.

If the front-end wasn't designed to work with SQL Server - and it obviously
wasn't - then it is likely that there would be other issues anyway.

--
Brendan Reynolds
Access MVP

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi all,
>
> We have a computer system in place which is built using a compiled
> front end (not sure what language it has been written in) which reads
> and writes data to an Access database. I have done a test migration of
> the system to our SQL server and linked all tables back to the Access
> database. The problem is that when I execute the front end, I get an
> error saying.
>
> You must use the dbSeeChanges option with OpenRecordset when accessing
> a SQL Server table which has an IDENTITY column.
>
> Has anyone any idea of a workaround to this as the system is quite old
> and not really formally supported anymore.
>
> Is there any workaround for this?
>
> Thanks
>
> Simon
>