Many organizations rely on this relational dataset to power reporting tools such as Crystal Reports and other analytics platforms. These reports support critical needs like board reporting, campaign tracking, and operational dashboards.

Removing this capability would force organizations to rebuild years of reporting infrastructure. Small and mid-sized advancement shops in particular often lack the staff, budget, or technical resources to recreate complex reporting within the limited capabilities of native RE NXT tools

We too have several very complex reports that run through Crystal Reports and require files exported from Raiser's Edge as mdb files. These reports are vital and way too complicated to recreate another way, especially given staffing and budget constraints. I wouldn't even know where to begin.

MDB files are a foundational component of our data model in Power BI. Two years ago, our Blackbaud Success Manager advised us to explore external software to overcome the many shortcomings of Raiser’s Edge reports. This required a substantial investment in training and labor, and the resulting model depends on MDB files for several one-to-many relationships that are highly relevant to our organization. Revoking this feature threatens to undo that investment and leave us without a solution. Raiser’s Edge cannot replicate these reports. Furthermore, the SKY API is not a viable alternative as a data source, presently, as key one-to-many fields, like membership transaction history, require separate API calls per transaction (setting aside the added labor of extending the connector logic).

We, too, use .mdb for multiple exports and hope it can be included in Webview before Database view is gone.

Glad I'm not the only one. Being advised to learn power BI and recreate years of work is not feasible.

The issue also affects our 13 custom reports. We currently export in MDB format, specifically Microsoft Access 2000 Database and mostly in the one-to-many option. Switching to another system would require significant training and re-creating all reports. Then add the difficulty of getting IT department buy-in for access to Power BI or Power Automate as a small school.

Almost all of our export needs are to MDB files, mostly in the one-to-many option. I can't imagine the time and effort it will take to replicate our reporting and data needs without this functionality.

We need the same functionality we had in db view. While not the most used format, there are times when data needs to be looked at, reported on, analyzed, etc. in more complexity than a flat format allows. This is the only way to get data out in a relational format from the front-end of the system. Please don't take RE backwards by removing this useful capability for which there is no reasonable alternative.

We rely on the Blackbaud Report Writer database (MDB) with Crystal Reports to generate complex reports and letters—beyond what standard RENXT reporting tools and complex Word merges can handle. As a small team, losing MDB export capability would mean manually creating each item, since alternatives like Power BI or Power Automate require leadership and departmental buy-in, significant time to learn and implement, and financial resources we simply don’t have.