I took the liberty of copying this to the Drupal4lib list, which is probably the best place for it.
A lot depends on how the fields are stored. In Drupal 7, field reuse is very important. If all of your *Description* have the same machine name, say field_description, then there will be a discrete table for that field and creating a view is pretty straightforward. It there is a field_screening_description and a field_class_description, then your view (a query) will be more complex. This is not to say that building it is that much harder, just that the tricky part is combining the fields.
Again, with the caveat is that I know almost nothing about your site, for a calendar-centric site as this appears to be, my inclination is to have a date (or event, etc.) content type along with content types for the types of events, like screenings or classes. I would likely take it a step further and create a type for course, as well, assuming that there is more than one class per course. I would pull these together using node relationships. The structure is a bit more intricate, but pulling reports like calendars becomes easier and more reliable.
For a major site, I forgo node content types in favor of entities.
> On Feb 23, 2015, at 11:08 AM, Rob Dumas <[log in to unmask]> wrote:
> Right now, my partner and I are building a site for a local arts education
> group using a design started (but left unfinished) by someone else. The
> site is built using Drupal 7 with Views/Fields/Panels.
> There are a few content types used in the site:
> ## Screenings
> A Screening has a number of Fields such as *Director*, *Description*,
> *Featured Image*, etc. It also contains a Field Collection called Screening
> Dates, which allows the editor to attach multiple
> datetime/location/tickets-url sets.
> ## Classes and Class Sessions
> A Class is a general content type which contains general info about a
> course: *Title*, *Description*, *Tuition*, *Instructor*, etc. A Class
> Session asks the editor to select a Class (or fill in a field for "one-off"
> sessions) and includes fields for *Registration URL* and *Class Dates*
> (multiple entries allowed).
> ## Where We're Stuck
> The client wants a Calendar which lists all of the Screenings and Class
> Sessions. I can pull in the Class Sessions, but they only show on their
> first date, they show all of the dates on that one entry... and I can't
> seem to pull in the Screenings at all.
> Screenshots can be found in [this imgur album](http://imgur.com/a/fwUv8).