Automate or Queue Export of One-To-Many MDB

Jeffrey Wat · July 2015

Has anyone found a way or developed a workaround to be able to automate or queue an export that produces a one-to-many MDB file? We have some exports that we use regularly that can take from 15 to 30 minutes to complete. It would be helpful that these exports could be automated to complete in the morning or overnight before staff arrive on the morning that the export is needed.

JoAnn Strommen · July 2015

BB has some kind of optional module ($$) that provides a queue user can run overnight. I know it was available as they tried to hook us up with it a couple of years ago. Assuming it's still an option out there.

See knowledgebase for more solutions: How to use Queue

Jeffrey Wat · July 2015

Update: if you schedule the queue to run with an output data format of Blackbaud Report Writer Database, the queued export runs fine. The problem there is, users with MS Access versions of 2010 or greater will receive a warning when they attempt to use the MDB. When exporting using queue with an output data format of MS Access 2000, the queue fails. When an output file of MS Access 2007 is specified, the queue fails and an exception report is generated.

Joshua Bekerman bCLO bCRE · July 2015

Does the queue work when run manually/on demand?

Debra Holcomb · July 2015

I'm a pretty heavy automated queue user and I love the feature. It sound like in this case it's an MS Access issue, not a queue issue. If you google "disable Access security messages" you'll find some responses in the Microsoft community that might be helpful. I don't use Access enough otherwise to provide any other suggestions.

John Heizer · July 2015

Another option is to use an intermediate Access database that does nothing more than link to the tables in the MDB that gets created by RE. End users open that intermediate database to get at the data they want and it shouldn't result in any error messages from Access. It also has the advantage of letting you create queries and reports in Access that don't get overwritten every time fresh data is exported from RE.

Jeffrey Wat · July 2015

Josh Bekerman:

Does the queue work when run manually/on demand?

When Data Format Microsoft Access 2000 Database is selected, no; running the queue on demand does not work.

Jeffrey Wat · July 2015

John Heizer:

Another option is to use an intermediate Access database that does nothing more than link to the tables in the MDB that gets created by RE. End users open that intermediate database to get at the data they want and it shouldn't result in any error messages from Access. It also has the advantage of letting you create queries and reports in Access that don't get overwritten every time fresh data is exported from RE.

I do use this tactic for other exported DBs. I have tried this for this export, and it looks like this is going to be the best workaround for this particular export "problem." Thanks all for your responses.

Automate or Queue Export of One-To-Many MDB

Comments

Categories