This is sort of a continuation of this thread -but I'm changing my approach.
I've been trying to figure out Bob's advice of creating a form where users can enter a semester/year and run different reports based on the criteria entered on the form. I know in the previous thread I asked about dates... but that is why I'm changing my approach. Some of the tables require a "date" field entry... while other tables only make sense to relate a "semester" and "year" to. Originally, I would have liked for users to have been able to enter a beginning/ending date OR semester/year into the form and the reports run off of that, but I soon realized that was way too complicated for me.
I have a table called "tblSemesterLookup" that contains the following data:
[Semester][BeginningDate][EndingDate]
Fall---------8/15-----------12/15
Spring------01/10----------05/10
Summer----05/13-----------08/10
Next, I have a form that contains a listbox that calls the data from [tblSemesterLookup].[Semester], and a text box for entering a year.
I decided I would like to do all searches based on a Semester Year which means, queries that include a "date" field will need to somehow figure out which semester that date corresponds to - and I would like it to do this by referencing tblSemesterLookup (so that dates can be changed later if needed).
Problem #1: How to keep track of the choices entered in Semester and Year by the user. I created "tblDateChoices" with fields [SemesterChoice] and [YearChoice] thinking this could be a place to store their choices, but I can't seem to get that to work with the form. It keeps saying "#Name?" in the boxes. Maybe it doesn't like my lookup? I'd like to know if this is even a good approach also.
Problem #2: How to get a query to run based on the criteria entered by the user. (And if the particular query to be run includes the date field, be able to relate the date to a Semester and retain the year entered to run the query by.)
At this point I've over-thought the problem so much I've confused myself.
I'm quite happy to have gotten it all written out and hoping it makes sense to you guys (and gals). Help? 
I've been trying to figure out Bob's advice of creating a form where users can enter a semester/year and run different reports based on the criteria entered on the form. I know in the previous thread I asked about dates... but that is why I'm changing my approach. Some of the tables require a "date" field entry... while other tables only make sense to relate a "semester" and "year" to. Originally, I would have liked for users to have been able to enter a beginning/ending date OR semester/year into the form and the reports run off of that, but I soon realized that was way too complicated for me.
I have a table called "tblSemesterLookup" that contains the following data:
[Semester][BeginningDate][EndingDate]
Fall---------8/15-----------12/15
Spring------01/10----------05/10
Summer----05/13-----------08/10
Next, I have a form that contains a listbox that calls the data from [tblSemesterLookup].[Semester], and a text box for entering a year.
I decided I would like to do all searches based on a Semester Year which means, queries that include a "date" field will need to somehow figure out which semester that date corresponds to - and I would like it to do this by referencing tblSemesterLookup (so that dates can be changed later if needed).
Problem #1: How to keep track of the choices entered in Semester and Year by the user. I created "tblDateChoices" with fields [SemesterChoice] and [YearChoice] thinking this could be a place to store their choices, but I can't seem to get that to work with the form. It keeps saying "#Name?" in the boxes. Maybe it doesn't like my lookup? I'd like to know if this is even a good approach also.
Problem #2: How to get a query to run based on the criteria entered by the user. (And if the particular query to be run includes the date field, be able to relate the date to a Semester and retain the year entered to run the query by.)
At this point I've over-thought the problem so much I've confused myself.

