I am writing from the development department of a community music school and I am surprised that this is a request that appears not to have been addressed yet because it crosses so many aspects of ANY work within relational databases. My organization, for instance, relies on a unique identifier to pair donor family records in the fundraising database with student enrollment data in the student family database in order to perform imports and to create mailings - we are a newer ASAP customer and are just learning that it appears that we can no longer sync our databases using the one unique family-identifying ID. This impacts our organizational fundraising efforts in a profound way, down to and including effective fundraising mailings, donor trend analysis, and being able to recognize which donors are student families and alumni families. Please consider this a second strong and urgent request to add Family Account ID to the enrollment report and the student report. Because Family Account ID is the internal relational key in ASAP between all family member records (if I'm understanding this field correctly), it is beyond imperative that this be a functional field for reporting and, honestly, I would love to know why this is a field that we cannot access across the majority of the reports or see in the family profile page given how central and basic it is to the functioning of the database and how it ties all records together.