Your statement that you're a Newbie implies that you intend to stick
with Access and become a developer at some level. This response is
based on that assumption.
There are several Access related newsgroups. Almost all of them have
names that indicate the area of interest on which they'd like to
focus: tablesdesign, forms, formscoding, modulesdaovba, etc. We're
not sticklers for disciplined posting but it is welcomed and there is
a benefit to the poster and the responder in so doing. The most
obvious reason being that responders (all of whom volunteer their
efforts and most of whom have real, paying jobs elsewhere) have
limited time and may decide that they'll concentrate on just a
particular area. If your issue really belongs in that area but you
posted it elsewhere then that responder may never see it. This
newsgroup (microsoft.public.access) is of the "omnibus" class which
welcomes issues from all over the Access map.
These newsgroups exist to help developers at any level of expertise to
solve a specific Access issue with which they are having difficulty.
There are a couple of newsgroups that are very useful for newbies:
microsoft.public.access.gettingstarted
microsoft.public.access..tablesdesign
Another extremely valuable resource is:
www.mvps.org/access
it is chock full of Access lore.
To the question in your Subject line: "Sure"
But, the information you gave in the body of your post is
insufficiently detailed regarding your schema (data design) to allow
recommending that you base it on your current design. A little
research on relational database design will reveal correct design
principles. Before you start adding functionality your data should be
in 3rd Normal form. Correct data design enables creating cost
effective and maintainable applications. Poor design will have you
scrambling back to re-do some part of the design in order to add new
functionality. Before you can get the data design correctly
implemented, you must have at least a paper design of your
application.
Building on the basis above you can get to the point where you can
enter the Requestor's name and come up with a list of all of the
quotes ever made for that Requestor. That list can be further refined
to display a list of past quotes on each item inversely ordered by
date. Either list above could be bounded by dates so that you show
only those quotes for the last xx Years or months or ??
Be aware that Access has a long and steep learning curve. If you want
to learn Access then be prepared to devote several person weeks of
effort to get from scratch to where you want to be. Note that doesn't
mean an hour or so per day for several weeks. It means several weeks
of effort. It will be well worth the effort when you get there.
Welcome to the world of Access development.
HTH
