Click for Index

Quadrant Systems RASWIN - Release Notes 2016

2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014

1.0.5996 2025-09-10 12:00

August 16th, 2016

  1. A field name for the TRANCODES table in the QSDATABASE_DEF table was found. This caused a error to happen when you tried to add or update a transaction code. This version adjusts the field names automatically, but you can also just manually correct the field name value via table maintenance if you are not prepared to upgrade to this verison.

    Use

    Maintenance→Table Maintenance→QSDATABASE_DEF table.

    Then type TRANCODES in the white box at the lower left corner and hit the enter key.

    Scroll down to field # 35, and make sure the value for the column name is SKIP_DESCRIPTION (an earlier update left the N off the end of the field name).

    Then just press ENTER to save the record.

  2. Starting with this release, the RASWIN program will verify and update (if needed) the QSDATABASE_DEF table column names whenever table maintenance or table exports are done. Previous versions relied on the values in this table being correct. This table is used primarily to limit the size of certain fields and to provide customized default values for each field. Earlier versions did this also, but the functions used were not fully compatible with very old versions of SQL Server, which, unfortunately, a few RASWIN users are still running.
    3. The RASWIN database includes tables that track what workstation started up and when, and what version of the program was in use at that time. The program has been adjusted to delete records in these tables from prior years. It works as follows. When the purge takes place, the system checks the current year and subtracts two years from that So, in 2016, any records from 2014 and before will be deleted from the version logger tables. When 2017 arrives, any records from 2015 or before will be deleted.

August 2nd, 2016

  1. This version includes logic to build views that may be missing. These are required for certain aspects of transaction processing and also for most reporting functions. The program checks for each one at startup, and if it is not found it will create it. If the view already exists, the creation step is just bypassed.
  2. Changes to the custom interfaces for HDL Business License and Accela Permitting were made to bring the current version of RASWIN into synch with those programs. These are specific to a single user site.
  3. Enhancements to the utility lookup functions have been made to enable special behavior as far as padding the account number entered by the user with leading zeros, adding a wild-card in front of the entered account number, and an option to utilize custom SQL queries to retrieve the requested data with custom sort options.

    Please refer to this link in the user manual for full details on these three options. The new options start with the reference to "LOOKUP-UB-DEFAULT-PAD-ZERO-SIZE"

June 9, 2016

  1. An issue was found in the CASH RECAP REPORT that created a problem when requesting TOTALS BY REGISTER. This has been corrected in this version, with the side benefit this data is now loaded into memory at program startup instead of requesting it from the database each time it is needed. Searching through the list in memory is much faster than doing a database call. To ensure that this information is current the in-memory list is updated automatically at periodic intervals as well as when manually requested by the "RELOAD LOCAL TABLES" file menu option.
  2. This version incorporates a few new stored procedure generation routines which will automatically run the first time the updated program runs. This eliminates the need to run the SQLUPDATER.EXE program when doing updates. The scripts that are run are stored on the workstation in the 
    c:\programdata\quadrant\downloads
    directory and will be installed there when the setup program is run.

    The first time the new version starts on the first workstation that runs RASWIN it may be a few extra seconds / minutes for the main menu to appear. As each adjustment to the tables, stored procedures and views is made an entry is made into a new database table that will record the fact that the update has been completed. On subsequent startups, this table is checked so that only those steps that have not been previously completed will be performed.
  3. Extra checking on the payment method entered on the payment screen is now performed. Normally this is selected from the drop down list of methods, so the end result was a valid entry. However, if you were quite speedy on your entry and typed in a non-valid method, the program would accept it regardless of whether it was valid or not. We are not certain when this error first came into being, but this updated version does additional tests to insure the entered method is a valid one.
  4. A new feature has been added to the utility billing lookup function (currently only those that utilize the LOOKUP_UB table -- others may be added in the future). This allows you to optionally do a 'SOUNDEX' type search if your version of SQL Server supports it. Earlier versions of the RASWIN program did not allow this option.

    The SOUNDEX function converts a name to a short numeric value that provides a way to compare an entered search criteria (e.g., SMITH) to other names that SOUND LIKE it (e.g., SMYTH, SMITHE, etc.) When you do a search based on a specific name using the LOOKUP_UB table, the progrma will display a check box to the right of the search value, as shown below:

    When the Soundex Search option is not checked, the program will find names that match your search criteria, which as always, can include wild cards. For example, if you entered SM*TH as the search criteria it would match any names that start with SM, then contain any other characters, followed by TH, such as SMITH, SMYTH, etc. If you use the Soundex Search option SMITH would find names that SOUND like SMITH (and some others that are close, but not exaclty a perfect match. For example, this is a a few pages of the returned names, so SMITH as your criteria may bring something like this, depending on what's in your database:


    The results are not 100% guaranteed to be exactly what we all might think "sounds like", but it can be very useful for search for names when you are not quite sure how they are spelled. Another example: ANDERSON, gives results like these:


April 15, 2016 - Version 1.0.4731

  1. A minor change related to the RECPRO PARKS AND RECREATION import function has been completed. In earlier versions there was an option to regenerate the TRANCODES_HOST_TO_QUAD table on the import screen. This function loaded a completely new set of entries in the table using the CR_ACCOUNT number and TRAN_CODE from the TRANCODES table.

    This has been modified to permit you to specify to use either the TRAN_CODE in both fields, or to load the CR_ACCOUNT and TRAN_CODE fields into the HOST_CODE and QUAD_CODE fields, respectively. There is a setting that controls this option.

    There is a second setting that you can use to turn off the regenerate screen option completely, so that once you have the settings the way you want them the program will not be regenerated unless you reactivate the option. These two settings are:

    RECPRO-FORCE-REBUILD-ALLOW      YES or NO

    RECPRO-HOST-TO-QUAD-FORCE-REBUILD-MODE      TRANCODE or ACCOUNT

March 18, 2016

  1. A few small changes were made to support a custom transaction data import file specification related to B&O tax payments for one of our clients.

February 18, 2016

  1. We recently had a customer discover that they had connected a couple of workstations to a test copy of the RASWINSQL database on a test server instead of their production server. When the ODBC settings were corrected and these workstations resumed posting receipts an overlap in receipt numbers resulted, making it a challenge to bring the transactions posted to the test server into the production server.

    Beginning with version 4711 the RASWIN program now checks the server to which you have connected to a setting in the database which indicates the production server name.

    If there is a difference between the two settings, a warning message will appear, as shown below:

    If you answer YES, the normal login screen will be shown:

    Note that the message:"Non-Production Server" and it's name will be shown in yellow as an additional warning, at the bottom of the login screen. The FIRST time you log in following installation of this version of RASWIN you will see this message, because the program has no way to know what your production server name is until you tell it. (see below on the setting that defines this value) so you will have to click YES to proceed and then adjust the setting in the tables.

    Once that is done, the workstations should see a 'normal' login screen, with a 'green' bar at the bottom indicating that the server it has actually connected to matches the defined production server name setting in the database.

    Since the application does not know what your server name should be, it will create a default entry, and the FIRST time you log in after updating to this version of the program you will see the warning shown above. It will be necessary to manually adjust the setting in the MISCPARMS table so the correct server name is recorded. This will only need to be done one time (unless and until your server name changes). The setting is shown below:

  2. A new report has been created to generate a list of the DEPTCODES table entries. It is available on the Main Menu⇒AUDIT menu and should appear at the bottom of the list. It is called DEPTTRANS XREF REPORT. To run it you simply click on the menu option and the mouse point will turn to an hourglass, then in a few seconds a dialog will appear asking you to "press OK to View/Print" or to "Cancel". When you select OK, you should see a report similar to the one shown below:


    The title bar listing your department codes will automatially list all of them found in the DEPTTRANS table and then the TRANCODES that exist in the DEPTRANS table for each of those departments will be listed down the left side of the report. If a specific TRANCODE is defined as being allowed to be processed in that department it will have an "X" in the grid. If a TRANCODE is invalid (that is, does not exist in the TRANCODES table, the TRANCODE column for that one will be shown in RED.

    Depending on the number of entries in your trancodes table, this list could be quite long. For this reason the column headers are repeated every 35 lines, however, we have thus far been unable to get page-breaks to work correctly for both the CHROME and Internet Explorer browsers; we'll continue to work on this issue.

February 5, 2016

  1. A small change has been made to the CASH RECAP REPORT and a couple of other reports that require you to select the register # to be reported on. In older versions the program would look at the list of registers defined in the license table and include them all in the list of registers that could be selected, including those that are not licensed for transaction processing (e.g., inquiry or reporting only workstations). It now looks at your transaction history to determine which registers have actually processed transactions and adds only those registers to the list of registers available for reporting.

    In a future release we plan to perform a similar function for the DEPARTMENT CODE and CASHIERS list so that it will not be possible to filter based on those criteria if there no applicable transactions. There is currently no planned schedule for this modification to be completed.

January 19, 2016

  1. A change to the QUICK REPORTS function has been made to insure that your simple SQL query requests are properly interpreted by SQL Server when the request is submitted. In earlier versions queries using the variable parameter option were not working correctly when the variable parameter was not the last portion of the SQL request.

    There is a specific list of tables/views that can be queried using this reporting function which is documented in the table maintenance section on Quick Reports. This can be reviewed here: Quick Reports
  2. It was discovered that when the backspace key was pressed in the description field on the transaction entry screen it was causing the cursor to move to another field instead of moving the cursor to backup with the data in the field itself. This has been corrected.

2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014