A
Axel Dahmen
Hi,
I've updated an Access 2000 database using DTS, having "Insert Identity
Columns" set to true.
My problem: The AutoValue field has not been updated correctly. When I now
add a new row manually within Access, instead of providing
(a) "SELECT MAX(AutoValueColumn)+1 FROM MyTable" ,
Access gives
(b) "SELECT COUNT(*)+1 FROM MyTable"
as the new AutoValue value !!
In the original SQL Server 2000 tables some rows had been deleted, so (a)
yields a higher value than (b). What I actually need, of course, is (a).
The AutoValue value gets incremented by one with every insert failing, but I
tend to believe that this is NOT the right way to move the AutoValue field
to its correct value manually.
Repairing and compressing the .mdb file doesn't change anything.
Is there a way to have Access correct the AutoValue fields in the database?
TIA,
Axel Dahmen
I've updated an Access 2000 database using DTS, having "Insert Identity
Columns" set to true.
My problem: The AutoValue field has not been updated correctly. When I now
add a new row manually within Access, instead of providing
(a) "SELECT MAX(AutoValueColumn)+1 FROM MyTable" ,
Access gives
(b) "SELECT COUNT(*)+1 FROM MyTable"
as the new AutoValue value !!
In the original SQL Server 2000 tables some rows had been deleted, so (a)
yields a higher value than (b). What I actually need, of course, is (a).
The AutoValue value gets incremented by one with every insert failing, but I
tend to believe that this is NOT the right way to move the AutoValue field
to its correct value manually.
Repairing and compressing the .mdb file doesn't change anything.
Is there a way to have Access correct the AutoValue fields in the database?
TIA,
Axel Dahmen