Chuck,
Thank you also for your input. I was able to transfer to Excel, and do
several passes to sort with no problem. But now I'm curious about what you
said of database normalization, what is that? I'm not familiar with that
term. My database in Access is in table format, with all my styles sorted. It
was just that I wanted certain styles within the same table to be sorted
fifferently without affecting the sort order of the rest of the records
within the same table.
The data in an Access table does not have to be 'sorted' in any particular way.
Therefore, it doesn't have to be 'resorted' every time new data is entered.
The sorting is done when by a report or a form when it is opened to display one
or more records.
Normalization basically means that you don't enter the same data over and over
again in a table. It is nor essential, but it is good practice.
Example: In a table with people and address you don't want to enter the same
city and state for a hundred different people. You would set up a table with
fields for zip code, city, and state. You would make the zip code a Primary
Key in that table. Then in the 'main table' you would enter only the zip code,
which is called a Foreign Key. The two tables are "related" Primary Key to
Foreign Key. When you make a report, Access uses the Foreign Key in the 'main
table' to 'look up' the related city and state. Since there is only one entry
for each city and state, it can not be misspelled in the data entry process.
Zip codes are not the best example because one city can have more than on zip
code, but it is easy to visualize. Actually a zip code only denotes the Post
Office for the area where the individuals' goes through. It is possible for
several small towns to have a zip code with the same first five numbers, but
when that happens, the last four numbers in the 5+4 zip code nomenclature will
be different. This situation can also happen within one city if it is very
densely populated. The last four numbers denoting an area that the post office
services.
If you see the same data in several fields for many records, there is a good
chance that it should be pulled out and placed in a related table. Again, not
necessary, only good practice.
Chuck
--