Well, I created this db on the fly and needed to ensure that the data types were managed separately... each of the separate data types needed to have a unique ID that is specific to the data type... The data types are alphacategories that go from A to V; each one represents a different type of stored data and we need to track the same information for each of hte data types, thus the need for the same data in each of the tables A through V except the alphacategory.
The goal is to have the alphacategories, A for instance, enumerate each record consecutively then have the same thing happen for each of the other alphacategories/data types. So, if we had 500 records for category A - they would be numbered sequentially like this A10001 to A10500, and 300 records in category B, they would be numbered in the same fashion, i.e. B10001 to B10300. Thus, each data type A-V will have its own group of unique alphanumerics assigned to it.
I din't come up with the idea, only the solution to data entry to accomplish this goal in naming convention for each of the data types. Do you have any other suggestions on how to do this?
---
Why 22 tables exactly the same?
The essential concept of a Relational Data Base Management System (of which Access is just one) is that you only store ONE piece of information in ONE place.
If you are locked into have the database structure non-normalised, you could explore using a Union query first to group the data, then run the Append query.
Have a look, though, at these tutorials: Database Normalisation and Table Structures and Basis SQL Syntax for Access queries
Regards,
Scott