News Categories
RSS Feed
News
Apr
21
Version 2016.250 Released - Report Runner Batch and Report Runner Viewer
Posted by Jeff-Net Fan Support 1 on 21 April 2017 08:40 AM

Batch:

  1. NEW: You can now run a pre-batch and/or post-batch SQL call (update, insert, or execute a stored procedure). You configure the SQL under the Tools menu (Global SQL). You configure what SQL to run in your batch-specific INI settings (use right-click menu to see new settings). Note, if your pre-batch SQL fails, your batch will NOT run.
  2. NEW: Created an INI option to modify how XML files are read (XMLReadMode); this setting is utilized by support when necessary
  3. NEW: SuperBatch trigger tree viewing can not filter only good triggers or only bad triggers; previously viewing both good and bad triggers sometimes gave a false positive that triggering was in an endless loop
  4. Updated: The batch-specific INI setting jnRemoveBlankLinesFromOutputFiles was modified to allow for setting a minimum length a line in a text-based output file should be. Previously this feature would simply remove blank lines. This new feature should not be overlooked. It helps remove bad data from CSV-type, text-based output files (stuff like lines with only commas. For example if all output lines should be at least 100 characters wide, just set the value to 100 and if the length of the record is less than that, it will be deleted. This is a really slick, new setting.
  5. Updated: More temporary file cleanup added; we found a number of places in our code where Windows temp files were not being deleted. For some users, this was causing an issue with Windows temp file space filling up. We also fixed an issue where some Windows temp files were getting created and were never used.
  6. Updated: Fixed an issue where some post PDF file processing was being called even when unnecessary. The file was not getting incorrectly modified, but it was unnecessary memory overhead. For some users, it triggered memory errors.
  7. Updated: Analyze/Find/Replace in Tools menu now defaults to ALL files/types
  8. Updated: Default PDF file attributes changed so all optional features are enabled by default
  9. Updated: Added additional log file message to assist with debugging. We also fixed some incorrect/misleading log file messages.
  10. Updated: We are now shipping SP20 (service pack 20) of the Crystal runtime engine in our FULL installer. We used to ship SP3. We still believe SP3 is the most stable, but SP20 includes a number of necessary features to work with newer versions of SQL Server and newer versions of Crystal Reports. If SP3 (or any other service pack) is working for you, there is no reason to install SP20.
  11. Updated: An exit code of 2 is no longer considered bad. It is only a warning. It is not a failure (a 1 is a bad exit code). This impacts triggered SuperBatches and post-batch SQL execution (that's why we made the change). 
  12. Updated: We are now utilizing a new licensing server. Technically the server is the same, but the IP address changed. If you want us to track the specific machines you activate our software on, you must be on this version or later.

Viewer:

  1. NEW: Added an optional, new, printing method. Due to some recent OS changes, some users are unable to print using the older/default print method. We have created an INI option (UsePrintMethod2=1) to enable this feature.
  2. NEW: New INI options added to configure Viewer (HideThereIsNothingToPrintMessage, HideExportBrowseButton, HideExportButtonInExport, DoNotOpenWindowsExplorerAfterExport, HideExportAndOpenButton)
  3. Bug Fix: Prevent auto-close from running during printing, exporting, or once close process has started
  4. Updated: More temporary file cleanup added; we found a number of places in our code where Windows temp files were not being deleted. For some users, this was causing an issue with Windows temp file space filling up. We also fixed an issue where some Windows temp files were getting created and were never used.
  5. Updated: Added additional log file message to assist with debugging. We also fixed some incorrect/misleading log file messages.
  6. Updated: We are now shipping SP20 (service pack 20) of the Crystal runtime engine in our FULL installer. We used to ship SP3. We still believe SP3 is the most stable, but SP20 includes a number of necessary features to work with newer versions of SQL Server and newer versions of Crystal Reports. If SP3 (or any other service pack) is working for you, there is no reason to install SP20.
  7. Updated: We are now utilizing a new licensing server. Technically the server is the same, but the IP address changed. If you want us to track the specific machines you activate our software on, you must be on this version or later.

---

Due to the licensing server IP address update, this update is considered semi-critical. You can download 2016.250 here:

https://jeff-net.com/downloads

---

Note, we had a number of users testing/using in-between releases via downloads recommended in support tickets. If you're using a version after 2016.230 and before 2016.250, please update immediately.