Crystal and Queue alternatives

Joshua Bekerman bCLO bCRE

Greetings,

We have about 25 Crystal Reports that are emailed on a schedule using RE Queue.  As the reports contain more data (as the year goes on) we are having more issues with the reports going out when they should.  When the Queue fails it is mostly because of "Memory full."  It's gotten to the point where Queue is not reliable and I wind up sending the reports out on my own.

Anywho, are they any other options to distribute Crystal Reports?  Currently all the reports are based on exports from RE and set up in Custom Reports.  However, I am looking into recreating the reports so they pull directly from RE Open (or whatever it is called now).  Is anyone distributing/emailing/sharing Crystal Reports without using Queue? 

 Thanks,

Josh

 

 

Mark Mathyer 2

Josh Bekerman:

Greetings,

We have about 25 Crystal Reports that are emailed on a schedule using RE Queue.  As the reports contain more data (as the year goes on) we are having more issues with the reports going out when they should.  When the Queue fails it is mostly because of "Memory full."  It's gotten to the point where Queue is not reliable and I wind up sending the reports out on my own.

Anywho, are they any other options to distribute Crystal Reports?  Currently all the reports are based on exports from RE and set up in Custom Reports.  However, I am looking into recreating the reports so they pull directly from RE Open (or whatever it is called now).  Is anyone distributing/emailing/sharing Crystal Reports without using Queue? 

 Thanks,

Josh

 

 

Josh,

We use the Queue in Raiser's Edge frequently to refresh report sets, but have not run into the "Memory Full" error.  We did quit emailing the results a few years ago - now we use the output features of the Queue to create PDFs on a common drive.  Then we just send out a link to the new report set. It seems to be a faster process, and it doesn't fill up everyone's mailbox with big reports.

Mark

Joshua Bekerman bCLO bCRE

Mark Mathyer:

Josh,

We use the Queue in Raiser's Edge frequently to refresh report sets, but have not run into the "Memory Full" error.  We did quit emailing the results a few years ago - now we use the output features of the Queue to create PDFs on a common drive.  Then we just send out a link to the new report set. It seems to be a faster process, and it doesn't fill up everyone's mailbox with big reports.

Mark

 Thanks Mark.  I'll give that a try.  How do you handle reports being saved with the same name?  For example, we have a daily gift report so we would need to rename the report PDF every day before the next one runs. 

 Thanks.

Mark Zarbailov

Josh Bekerman:

 Thanks Mark.  I'll give that a try.  How do you handle reports being saved with the same name?  For example, we have a daily gift report so we would need to rename the report PDF every day before the next one runs. 

 Thanks.

Hi, One way to keep report history is to run all scheduled reports to a folder where the Queue is installed. Then, sometimes after all reports are refreshed/ recreated, move/copy them to a common shared folder for users. During a move/copy procedure create folders for each day using a script language. If you have a good script, you can automate it using windows task schedule. I hope this makes sense.

Mark Mathyer 2

Mark Zarbailov:
Hi, One way to keep report history is to run all scheduled reports to a folder where the Queue is installed. Then, sometimes after all reports are refreshed/ recreated, move/copy them to a common shared folder for users. During a move/copy procedure create folders for each day using a script language. If you have a good script, you can automate it using windows task schedule. I hope this makes sense.

Josh,

Mark Z. responded before I did, but I agree with what he said.  We do have a few reports that we grab everyday & rename, but most go into a 'Staging Folder', and then get shifted to daily, weekly, or monthly folders before the next running of the queue overwrites them.