J
Jason Sharp
Having briefly parused, entries (posted 7/29) regarding this subject, I was kind of shocked by the argument that ensued after a good gesture. Truthfully, I found the gesture competively flawed, but was not impressed with the pseudo-eccentric approach initiated by the Access MVP.
I guess I'm a hobbyist! Here are some tips:
DataManagement:
- Make sure you run an export of data you wish to keep, before purging records.
- To adjust seed values: you will want to create a new single-field, single-record table with an autonumber field populated by a number 1 less than your desired first record. Then append this value via append query to your table from which you either purged records, or what-not...
- You can also use Excel or another spreadsheeting program to to manipulate exported data quickly, then re-introduce the data to the table from which it came.
Access '97:
- Simply adding a new autonumber field and deleting the old autonumber field should work just fine. If the new autonumber field is to be the primary key for records: of course, you will have to remove constraints of the old field first. And certainly any related table may be impacted by this change. This doesn't apply to custom seed values. Also, I think this is possible in Access 2000 as well.
I guess I'm a hobbyist! Here are some tips:
DataManagement:
- Make sure you run an export of data you wish to keep, before purging records.
- To adjust seed values: you will want to create a new single-field, single-record table with an autonumber field populated by a number 1 less than your desired first record. Then append this value via append query to your table from which you either purged records, or what-not...
- You can also use Excel or another spreadsheeting program to to manipulate exported data quickly, then re-introduce the data to the table from which it came.
Access '97:
- Simply adding a new autonumber field and deleting the old autonumber field should work just fine. If the new autonumber field is to be the primary key for records: of course, you will have to remove constraints of the old field first. And certainly any related table may be impacted by this change. This doesn't apply to custom seed values. Also, I think this is possible in Access 2000 as well.