1-many relationship filtering problem

[Default8129]

I have the following data model:

StudentTable - one row per student

StudentID	Graduated?	StartTerm	EndTerm
5	Y	21/FL	22/SP
6	N	22/FL	23/WN

StudentTermTable - one row per term enrollment for each student

StudentID	Term	Term Order (calculated column)	FTE	Program
5	21/FL	Start Term	1.2	Nursing
5	22/WN		1.2	Nursing
5	22/SP	End Term	0.5	Nursing
6	22/FL	Start Term	1.0	Education
6	23/WN	End Term	1.0	Accounting

With the relationship between these tables being 1-many based on the StudentID. There are also fact tables for Term, FTE, and Program. I actually have many fields in the StudentTermTable, all with their own fact tables, but this is a small sample of the information.

What I'd like users to be able to do is, for example, filter the report to show data only for our students who started full-time (FTE >= 1) and ended part-time-time (FTE < 1). So here I'd want to include student #5 (their starting term 21/FL enrollment was full-time and their ending term 22/SP enrollment was part-time), but I'd want to exclude student #6 (starting term 22/FL enrollment was full-time but their ending term 23/WN enrollment was also full-time). There are many fields in StudentTermTable that users might want to use to filter both the start term and end term: campus, athletic teams, campus organizations, housing status, various financial aid data, etc. so I need to give them the flexibility to filter both the start term records and end term records by all these term-specific fields.

I can't figure out what to do so that the report allows users to easily filter this way without making major changes to my data model. Currently the only solutions I can find basically require me to completely re-work StudentTermTable which is already very large (600,000 rows) and has many fact tables associated to it.

I could pivot my StudentTermTable so I have a StudentTermTable (StartTerm) and StudentTermTable (EndTerm). I could create compound fact tables (e.g. permutation of {"Start Term","End Term"} with each fact table) but then I'd basically double the size of my StudentTermTable table with these compound data fields. Neither of these seem elegant nor efficient to me.

Is there a good solution to this need?

[guibenassi]

I would recommend you to use measures that calculate count of students and filter all Date after Min(date) and all Date before Max(date) in segmentation.

[Default8129]

How would that solve this issue? If by "date" you're referring to the Terms then your solution would only work if I didn't need to additionally filter my students by the data fields attached to their terms.