I have successfully run for 7 years ASPX Order and Amendment Forms linked to an on-line Access 2000 database. For the first time ever the next sequential record (i.e. Order Number) has not been generated, such that the database (and therefore on-line datagrid
display) are missing number 869. Subsequent orders 870 and 871 have been accepted by the database without problem on the part of the customers, as far as I know.
Can anyone please suggest how such an anomaly could occur?
As far as I see, it seems that if you define a column that is of type identification step from 1 by 1, it will be a sequencial numbers of a list. But if you fail to insert some records or something else, the number won't be in sequencial again. And I'm afraid
you cannot change the state like this.
RedcarJohn
Member
380 Points
103 Posts
Access database anomaly
Nov 12, 2012 09:45 AM|LINK
I have successfully run for 7 years ASPX Order and Amendment Forms linked to an on-line Access 2000 database. For the first time ever the next sequential record (i.e. Order Number) has not been generated, such that the database (and therefore on-line datagrid display) are missing number 869. Subsequent orders 870 and 871 have been accepted by the database without problem on the part of the customers, as far as I know.
Can anyone please suggest how such an anomaly could occur?
RedcarJohn
hans_v
All-Star
35986 Points
6550 Posts
Re: Access database anomaly
Nov 12, 2012 01:25 PM|LINK
Either record 869 is deleted, or the INSERT statement to create record 869 failed.
Decker Dong ...
All-Star
118619 Points
18779 Posts
Re: Access database anomaly
Nov 13, 2012 12:27 AM|LINK
Hi,
As far as I see, it seems that if you define a column that is of type identification step from 1 by 1, it will be a sequencial numbers of a list. But if you fail to insert some records or something else, the number won't be in sequencial again. And I'm afraid you cannot change the state like this.