BBNC: Flat File (Why???)

Tom Klingman

We struggle constantly with BBNC in that basic constituent fields we can add to websites are limited to the constituent record.


We can't publish data from related tables (spouse information, relationship to education/schools, individuals), etc.


This severely limits our ability to host websites with comprehensive constituent data.


We can EMULATE data from related tables by using single constituent attributes (as in Sister 1, Sister 2, Brother 1, Spouse Email, Spouse Deceased?, Graduate Degree 1, Graduate Degree 2).


As you can imagine, this creates a HUGE amount of unnecessary constituent attributes for data that is/should be stored in related tables (RE is a relational database!!!).


But we're stuck with this flat-file construct with all the hacks we need to emulate a real database.


What is BBNC's rationale for not making related tables/information available in this product???


Thanks, Tom