C
Cheryl
The upsizing wizard in Access 2002 works well, with the exception of any
table with autonumber fields. I found this explanation in the knowledge
base:
Incrementing AutoNumber values in Microsoft Access (called "counters" in
previous versions) and the triggers created by the Upsizing Wizard to
emulate incrementing AutoNumber values (when upsizing to SQL Server 4.21
and 6.0) or the identity columns (created when upsizing to SQL Server
6.5) don't behave identically. In Microsoft Access, an AutoNumber value
is pre-allocated; that is, it is generated as soon as a user starts
editing a new record, before it is saved. On SQL Server, a trigger or
identity column generates the number only when the new record is saved.
If your Microsoft Access application depends on using the value
generated by an AutoNumber field before the record is saved, you will
need to redesign this functionality when upsizing to SQL Server.
Can anyone interpret that for me? Exactly how would I "redesign this
functionality?" Thanks for any insight you can give me on this!
table with autonumber fields. I found this explanation in the knowledge
base:
Incrementing AutoNumber values in Microsoft Access (called "counters" in
previous versions) and the triggers created by the Upsizing Wizard to
emulate incrementing AutoNumber values (when upsizing to SQL Server 4.21
and 6.0) or the identity columns (created when upsizing to SQL Server
6.5) don't behave identically. In Microsoft Access, an AutoNumber value
is pre-allocated; that is, it is generated as soon as a user starts
editing a new record, before it is saved. On SQL Server, a trigger or
identity column generates the number only when the new record is saved.
If your Microsoft Access application depends on using the value
generated by an AutoNumber field before the record is saved, you will
need to redesign this functionality when upsizing to SQL Server.
Can anyone interpret that for me? Exactly how would I "redesign this
functionality?" Thanks for any insight you can give me on this!