Yes.
Oh... you wanted details. Let me give this bit of advice. Start by designing things on paper using analysis pads. You must be able to define your data flow before you try to implement anything. This is because of a couple of "Old Programmer's Rules."
First, "You can't do it in Access if you can't do it on paper." Stated another way, if you don't have a detailed data flow diagram to show the source and destination of each item of data you need, you don't know enough to implement anything in Access.
Second, "Access won't tell you anything you didn't tell it first (or at least tell it how to tell you)." Stated another way, you need to know what you want OUT of the database - IN DETAIL - to know what you will need to put into the database so that it CAN tell you what you wanted to hear.
Now, the direct answer to your question. If you could design a data flow process that would lead to the result you wanted, you could implement it Access. What you described earlier seems to be within the realm of possibilities for Access.
