Batch

1. Log files are now 100% unique per start of Report Runner Batch. Previously, JNRRBLOG.TXT was always the "current" log file. This has changed. The problem with JNRRBLOG.TXT always being the current log file was if more than one batch was running at the same time, the same log file got written to by multiple batches. This can no longer happen. And when you go to the Debugging menu to view the current log file, it will open your current "unique" log file.
2. Additional feature added to the Notification Report to automatically add the debug log file for the batch if the batch does not run successfully. This automatic behaviour can be modified using a new INI setting under [Options] called AttachLogFileToNotificationReport=NO (it is YES by default). To automatically attach the log file to the Notification Report for successful batches, too, add AttachLogFileToNotificationReportOnBadRunsOnly=NO (it is YES by default).
3. Additional feature added to the Notification Report for reporting issues with bursting batches, too. We now have a bursting exceptions log file that will be automatically appended to the Notification Report. To modify this behaviour, under [Options], add AttachBurstExceptionsLogFileToNotificationReport=NO (it is YES by default). This new feature to report burst exceptions is great, especially when used with the batch-specific INI setting of NoFailOnBurst=YES. This allows your burst to fully run, even with exceptions, and you can handle the exceptions in the end. If you do not turn on NoFailOnBurst=YES, a bursting batch will stop running on the first exception.
4. Fixed a bug where bursting batches being exported to mail... if an error was encountered, the batch would fail, but the message would still say "Successful" as the last run message. This has been modified to say "Mail Error... check log file".
5. Added an error catch for users trying to (erroneously) open RPT files instead of XML batch files using the Open button. This would previously cause the application to crash and send us a ticket.
6. Added executable version and path information to log file when debugging is turned on from Debug menu. This information has always been available when debugging was on from the start, but the log was incomplete when debugging was turned on after application was running.
7. Added "ref=" parameters to Jeff-Net URLs opened from within the application
8. Disabled CC and BCC settings from being applied to the Notification Report for bursting batches

Viewer

1. Log files are now 100% unique per start of Report Runner Viewer. Previously, JNRRVLOG.TXT was always the "current" log file. This has changed. The problem with JNRRVLOG.TXT always being the current log file was if more than one user was running reports on a shared server at the same time, the same log file got written to by multiple users. This can no longer happen. And when you go to the Debugging menu to view the current log file, it will open your current "unique" log file.
2. Added executable version and path information to log file when debugging is turned on from Debug menu. This information has always been available when debugging was on from the start, but the log was incomplete when debugging was turned on after application was running.
3. Added "ref=" parameters to Jeff-Net URLs opened from within the application
4. Fixed a random bug where the directories/folders were not always being sorted alphabetically for all drives in the left-side directory/folder view.

---

This is not a critical update, but it is highly recommended!

http://www.jeff-net.com/download.htm

Batch

1. Fixed a bug related to random spaces in URLs, when report text is exported to our Newsletter format
2. Modified Notification Report logic, when added to a bursting batch, if sent by email the Subject for the Notification Report will be hardcoded to "Jeff-Net Report Runner Batch Bursting Notification Report ::: <burst file name". Also modified logic so custom headers and footers would not be included in body of Notification Report email.
3. Fixed an error message that contained double "[@"

---

Update can be downloaded from our Download page. This specific release is not considered critical, but if you haven't updated in a while, there have been recent critical updates.

http://www.jeff-net.com/download.htm

Batch

1. New feature added under Tools, Generate. We've added a desktop shortcut generator! This allows you to easily generate on-demand batches. It creates the shortcut on your desktop that you can double-click anytime you want to run that batch.
2. Auto-fix logic added to correct parameter date formatting issues. We have had a global setting available since the release of the product, but some users miss setting it. If there is a problem setting the date, this fix will automatically try the other format. And when we speak of formats, we mean MM-DD-YYYY vs DD-MM-YYYY. This fix has nothing to do with date/time stamps. It's an internal issue related to setting date values for parameters based on where you are in the world and what your system date format is.
3. Added and updated messages related to editing your burst settings and test viewing your reports in the Job Edit window. If you have any errors editing your burst settings, some of the messages have been greatly improved as to what the error is.

---

This is not considered a critical update, but is definitely recommended.

http://www.jeff-net.com/download.htm

Batch

1. Fixed a bug with unknown database types that would cause the application to crash with some reports
2. Moved "running" status window just below center of screen. There are times when other applications show messages in the center of the screen and the status window was blocking it.

Viewer

1. Fixed a bug with unknown database types that would cause the application to crash with some reports
2. Moved "running" status window just below center of screen. There are times when other applications show messages in the center of the screen and the status window was blocking it.
3. Fixed a permissions issue with the free edition

---

http://www.jeff-net.com/download.htm

Note: If you've updated to 2012.20, this is considered a non-critical update unless you have reports that are not working correctly

Batch

1. "Do Not Run" calendars have been added. This allows you to specify that any batch never run on the "jnMaster" calendar or create an unlimited amount of custom calendars and specifically assign those to batches. The dates you specify are a simple format of MMDD. For example, if you wanted to keep batches from running on Halloween and Christmas, you could create a "MyHolidays" and set it to "1031, 1225". You would then set a batch-specific do not run calendar setting. (See bottom of this news release for Calendar settings to add to the bottom of your JNRRB.INI). Note, these calendars are not visually integrated in the Scheduler functionality at this time. The Scheduler will still show a batch "scheduled" to run on a certain day, but rest assured, if you have a do not run calendar set for the batch, the batch will start and exit successfully with a calendar message.
2. Fixed a bug when users right-click and use Run Job to run a parameter burst job
3. Fixed a bug where jnBurstEmail was not being processed in parameter burst jobs
4. Added additional log file messages for debugging any data connection issues
5. Added INI settings to override the Newsletter names in the batch job Destination Format list. This allows for users to change the name to something more descriptive when they greatly modify the default newsletter settings.
6. Added log file message to display parameter burst values (the entire list on one line)

Viewer

1. Added additional log file messages for debugging any data connection issues

---

Batch users should add the following section to the bottom of their JNRRB.INI file. Note, if you do a new install, you will see this in the file automatically. 

'-------------------------------------------------------------------------------------------
[Calendars]
'These calendars are used to NOT run a batch on a given date
'Format is MMDD (two character month and day for each required) - For example: 1225 is December 25th/Christmas
'Separate multiple dates with a comma - For example: 1225, 1128, 0214, 0101

'jnMaster is a SPECIAL calendar name. It is checked AUTOMATICALLY for ALL batches and will NOT run the batch if same date
jnMaster=

'This is checked only if you MANUALLY set "DoNotRunCalendar=<this calendar>" within your batch-specific settings/INI
Holidays=
MyDoNotRunCalendar=
MyWhateverCalendar=
MakeUpYourOwnCalendar=

---

http://www.jeff-net.com/download.htm