RPOWER.Reports Product History

From RPOWERWiki

Jump to: navigation, search

2014-07-16

  1. The Report Runner has been updated to support both SQL Server and MySQL databases.
  2. The Hale & Hearty Custom reports have been updated to support both SQL Server and MySQL databases.
  3. Change was made to Hale & Hearty 4-Week Sales History report so that the Salad Summary line now also contains Pre-Pack Salads.
  4. The Customer Zip Code listbox was removed from the Customer Label report. This report now works.

2014-07-14

  1. Resolved divide by 0 error in Daily Sales by Day report when calculating labor percentage.

2009-10-16

  1. Custom reports are functional once again. Changes to the user accounts to support SQL Server and auto-running reports had broken it.

2009-10-13

  1. Fixed a divide by zero error in the Daily Sales report. The divide by zero error would appear on the average check amount if the guest count was equal to zero. This was not a common situation, only happening on days when the export failed.
  2. This version removes the user restriction of viewing a single store within a consolidation group. A user can now view multiple stores within a consolidation group as long as the store serial numbers are separated by a | (pipe). Example:
1234|2345|3456

2009-07-15

  1. Fixed a bug that would cause the ReportRunner to not recognize any format other than pdf. Probably, the bug was introduced when I added the auto-run reports functionality.

2009-07-08

  1. Items in lists now display in alphabetical order.

2009-07-02

  1. This version has the ability to automtically run reports and email them to a recipient.
  2. Due to new work going on where reports are calling Transact-SQL stored procedures, MySQL is no longer supported when using RPOWER.Reports. We may, for a short period of time perform MySQL installs for services such as dinePoint. Serval is already compatible with SQL Server.

2009-06-26

  1. Added functionality to support RPOWER 2009 PUNS (Publicly Unique Numbers).
  2. This is the last release which works with MySQL.

2009-04-03

  1. Fixed a bug that was preventing calculation of certain calculated date parameters.

2009-04-02

  1. Updated the user interface to be compatible with Internet Explorer 8 Non-Compatibility mode (the default mode in IE 8)

2009-04-01

  1. Added a single page Daily Sales Report

2009-02-19

  1. The Select Options page now has drop-down lists for year and month selection as well as calendars

2009-02-03

  1. Added a back button to all pages

2009-01-21

  1. Updated the RPOWER.Reports website to work with MySQL ODBC driver 5.1 so it can support newer MySQL databases

2008-09-04

  1. Fixed a bug where a report ran on a single day would result in a blank report.

2008-09-03

  1. The RPOWER.Reports website now utilizes a prototype engine to render its pages. This engine is based on using an xml file to set up control positions and sizes. This allows the web page to be much more configurable, and allows for easier updates. Previously, this kind of stuff was done in code, meaning the layout of a page couldn't be altered.
  2. Utilizes datasets and xsd files so that the reports are no longer database specific. This is the first version which will run reports against either a MySQL or a SQL Server Database.
  3. The Crystal Reports Engine has been upgraded to Crystal Reports for Visual Studio 2008 which, I believe, is roughly equivalent to Crystal Reports 10.
  4. The user file has changed somewhat. The user xml node now requires a db_type, either MySQL or SQL_Server, and a cg. More information can be found in the Setting Up a New User.txt file located in the users directory.

2007-04-20

  1. The Select Options page shows either the store name or the store tag name depending upon whether tag name exists in the database.

2007-03-28

  1. The STOR attribute for each user must be the store's serial number. The STOR attribute used to contain the store mid, but that could not be gotten until after the store performed its first import since an mid is issued by the database. Using the store serial number, which is always available, users can now be set up with store restrictions at website installation time instead of only after the store performs its first import.
Views
Personal tools