Thank you for the quick reply. Allow me to expand on my goal...and (Yes, the data in the repeating fields are values entered in separate reps.)
This database is very large, and live (125K+ records) It's for gear needed for meetings. Each record is an "invoice" of gear.
I would like to be able to "mine" the data in two existing, repeating fields (10 reps; "ID", which happens to be the primary key, and "Equip Description") so I can track amount of gear in use, and gear needed for future events.(Related table is just an inventory list, related by the ID code)
I am assuming I need to separate the repeating fields in order to get a running count, or is there a way to do this with the existing structure?
Note:This database was not set up to track the gear very well, but it's what I have to work with...All fields are in one table except the gear list. (There are many other fields for random data, but not of concern to my project)
Due to the large number of existing records I don't thing migration is workable, although I like the idea.
I hope I am on the right track here, and thank you for any help or guidance.
Please let me know if I need to clarify...