control services · scs_report.docx 2017-03-08 page 1 of 59 scs_report help version – 01.03.18...

SCS_Report.docx 2017-03-08 of 59

SCS_Report

Help Version – 01.03.18 (2017-03-08)

SoftReport is a program that is used to obtain query parameters from the user and to run Crystal Reports. Crystal Report is a product of Seagate and not provided as standard with the Softcon products. It is used to generate the output of the report. Certain reports are shipped with SoftReport and additional report outputs could be designed with the Crystal Report product by Softcon or by certain distributors at additional charges. SoftReport consists of a server program SCS_RepServer.exe that is installed where the databases are located and generates the databases required by the client program SCS_Report.exe – performs sql queries on the daily log files and transfers the appropriate files to the local PC. SCS_Report cannot run without SCS_RepServer running. SCS_RepServer connects to SCS_Server to obtain password and report set-up information and cannot run without SCS_Server running. The user uses SCS_Report to select the desired report and to select query parameters and to view the report generated by SCS_RepServer. Numerous client programs SCS_Report can connect to SCS_RepServer. The reports generated can be saved in zipped HTML and optionally in HTML, MS Excel and RTF files. Four types of reports are possible:

LOG REPORTS Historical events. ACCUMULATION REPORTS Historical accumulation. AUDIT Historical edit changes. DATA REPORTS Current set-up and status.

The program is executed by double clicking on the SoftRep icon or by selecting the SCS_Report in the tools menu. SCS_RepServer must be running. All functions are PASSWORD protected. When SoftReport is run, a drop down list box is displayed, from which the required report is selected. On selection, the user sets the required query parameter(s) if required. Parameters have defined defaults (listed in reports.mdb) and could be fixed or variable (e.g. to-days date, date-1). Parameters could be list boxes pointing to other databases (e.g. Cardholder is a list of cardholder names). The design of the report is described in REPORT DESIGN. The report set-ups are stored in the database Report.mdb. Designing or modifying additions reports could require knowledge of SQL queries. See SQL queries for explanations and examples. Numerous STANDARD SOFTCON REPORTS are shipped with the SW. Numerous STANDARD CRYSTAL REPORTS, which used by the SoftRep to generate the report outputs, are shipped with the SW. Special changes are required when a number field is changed to text (e.g. card number is shipped as field type number, is required as text – typically for touch tags) – see number convert. When a report is run, the event is logged with the operator and report references. Changes to report designs are logged in the audit files (is audit is enabled for SCS_Server.exe).

SOFTWARE CONTROL SERVICES


1 PASSWORDS

When the program is executed, a password is required that gives access to the program and selections on the menu. User group, users and passwords are set in the program SCS_Client. An auto-logoff period and an auto password expiry period can be set in SCS_Client. Menus to which user groups have access to are set by administrators in the Tools/Menu Access dialog. Tools/Dialog Access sets what reports and what parameter selections the user groups can select and edit. Items that are visible to the user group are moved to the Member of block on the right by clicking on the item in the Not member of block on the left (multi-selections by holding in Shift – select all between, or by holding in Ctrl – selects or deselect selection) and

clicking on the move right button . Items are toggled between view only and editable by clicking on the icon. Batch selection for the report allows the current report setting to be set for multiple reports for the selected user group. Batch selection for the user group allows the current report selection to be set for multiple users – the item selection can be modified by selecting add or delete.

Logon is changed by entering the user name and password. Logon and logoff are logged.


2 LOG REPORTS Log reports are to obtain historical data; e.g. who entered area zone ABC between 20h00 last night and 08h00 this morning or who of department X arrived late this morning. Transactions are logged (is set to be logged) by the Softcon system to an MS ACCESS data table when it occurs. The system automatically creates a table per day, with the name yyyymmdd (where yyyy the year, mm the month and dd is the date), into a database created monthly, with the name LGyyyymm.MDB, in the directory C:\SoftWin3\Log. A record is added per transactions and consists of the following fields:

Ref.: A running event number for the day, equal to the record number. Date: The real date of the event (yyyy-mm-dd), e.g. 1998-03-16. Time: The real time of the event (hh:mm:ss), e.g. 12:35:40. Type: Event type, a number between 0 and 10000, e.g. 1=reader, 2=input, 3=output, 4=controller, 5=camera,

6=counter, etc. Type descriptions are defined in the table type in events.mdb. System: System is a number that defines which one of the type, e.g. reader 10 or input 1234. Status: The transaction definition number, e.g. 20=out of area, 50= changed to level. Status descriptions are

defined in table status in events.mdb. Xref: A reference number used in certain events, e.g. the card number. Value: A number used in certain events, the level value of input, or the value of a counter. Ref2.: When card/reader transactions are visitor cards, the visitor database reference is set in Ref2. Z1...: Certain events have additional parameters that are set in Z1 to Z7. Typically used by vending and card

maker events. SoftWin3 uses the date/time field containing date and time and has the additional field:

Alarm: Indicates an alarm event when set to 2. 1 indicates normal, 0 sets none and 3 indicates accepted. Log reports always have start / end date and start / end time parameters, and could have a combination of parameters referring the other fields. In order to accommodate limitations in Crystal report functions, SoftReport transfers records that pass relevant query parameters from the daily log table to a predefined table LOG in LOGGING.MDB. This table with links to other data tables as required by Crystal, is flushed of records when a new report is generated. The specific Crystal report is called with specific parameters (see REPORTS.MDB).

3 ACCUMULATION REPORTS Accumulation reports are to obtain historical time accumulation data; e.g. how many hours did John work last month. Readers within the system are set as clock in and clock out readers. When a cardholder enters via a clock in reader, time accumulation for that card is started and is stopped when the card exits via a clock out reader. Totals for the day, week and month are saved to an MS ACCESS file at the end of the accumulation day (as set in the GENERAL PARAMETERS set-up, e.g. at 23h00). The end of week (Monday is 1 and Sunday is 7) and end of month is also set in the GENERAL PARAMETERS. On the end of day, the system automatically creates a table, with the name ACLOG, in to a database created daily, with the name ACyymmdd.MDB (where yy the year, mm the month and dd is the date), in directory C:\SoftWin3\Audit. After the total is loaded, the card’s day total in the card database is cleared and at the end of week and month, the weekly and monthly totals of the cards are cleared. A record is added for each card with an accumulation total and consists of the following fields:

Ref.: A running event number for the day, equal to the record number. Date: The real date of the event (yyyy-mm-dd), e.g. 1998-03-16. Card: The card number. Day: The accumulation total for the card for the day. Week: The accumulation total for the card for the week. Day: The accumulation total for the card for the month.

Accumulation reports always have start and end date parameters, and could have combination of parameters referring the other fields. In order to accommodate limitations in Crystal report functions, SoftReport transfers records that pass relevant query parameters from the daily log table to a predefined table ACLOG in ACCUME.MDB. This table with links to other data


tables as required by Crystal, is flushed of records when a new report is generated. The specific Crystal report is called with specific parameters (see REPORTS.MDB).

4 AUDIT REPORTS Audit reports are to obtain historical data on edit changes made by operators. When SCS_SERVER.exe is started with the parameter /audit, system automatically creates an audit database when data is edited. A table is created with the name AUDIT, in to a database created daily, with the name AUyymmdd.MDB (where yy the year, mm the month and dd is the date) in directory C:\SoftWin3\Audit. A record is added for each database field changed by the operator and consists of the following fields:

Reference.: A running event number for the day, equal to the record number. DT: The real date time of the event (yyyy-mm-dd HH:mm:ss), e.g. 2003-12-25 21:59. Field: The Softcon ID if the field changed, e.g. F_CD_NUM. The ID are defined in the table FIELDS in

C:\SoftWin3\Config\Database.mdb. Primary: The database reference of the data changed (e.g. the card.reference for a card field that was changed. Old: What the data was. New: What the data is changed to. Criteria_1: Similar to old when field is number. Criteria_2: Similar to new when field is number. Operator: The reference to card_reference of the operator that made the change. Type: What change is made (1=update, 2=add, 3=delete). From_PC: PC reference that the change was made. Source_Host: PC reference that load the data to the audit file – used by SCS_DistrServer when databases are

synchronized. Info: Used by SCS_DistrServer when databases are synchronized. DT_Replicate: Date/time the data is synchronized, used by SCS_DistrServer when databases are synchronized.

Audit reports always have start and end date parameters, and could have combination of parameters referring the other fields. In order to accommodate limitations in Crystal report functions, SoftReport transfers records that pass relevant query parameters from the daily audit table to a predefined table AUDIT in AUDIT.MDB. This table with links to other data tables as required by Crystal, is flushed of records when a new report is generated. The specific Crystal report is called with specific parameters (see REPORTS.MDB).

5 DATA REPORTS Data reports are to obtain data from data tables and are not related to events (log transactions), audit or accumulation. The reports require no pre-processing of data tables and start specific Crystal reports with the required parameters.

6 REPORT.MDB All reports are defined by the table report in report.mdb, facilitating the addition of reports without requiring changes to software. A record per report defines the functions and parameters of the report. The general fields are:

Ref.: The report number, equal to the record number. Name: A description given to the report. These names are displayed in a list box when the user selects a report. Crystal: The name of the crystal report that is started by SoftReport. X_query: The string passed to crystal report. Parameters are parsed in to the string (see below). Log: Indicates if the report is a log or data type report, 1=log, 2=data, 3=accumulation.

The following fields are used by log reports and are used to filter records from the day table to the report table. In data reports, the fields are not used.

Sdate: Start date in the format yyyy/mm/dd, e.g. 1997/12/31. Edate: End date in the format yyyy/mm/dd, e.g. 1997/12/31. Stoday: Use to day’s date for start. Etoday: Use to day’s date for end. Soffset: Start date to day less. Eoffset: End date to day less.


Stime: Start time in the format hh:mm:ss, e.g. 00:08:00. Etime: End time in the format hh:mm:ss, e.g. 24:00:00. Swindow: Start time of the time window in the format hh:mm:ss, e.g. 24:00:00. Ewindo: End time of the time window in the format hh:mm:ss, e.g. 24:00:00. Log_query: Additional query string used to create the search SQL for the log files. Parameters are parsed in to the

string. The above fields are always used in the query and are not entered in to this log_query. The additional log query is relevant only to data in the log files, e.g. “AND (type=1)” for readers. If no additional filter is used, log_query is blank. See SQL queries. The report user can enter up to 10 parameters. These are parsed in to the log and crystal query strings. Data starting with a ~ character, indicates that the user can change the data and is referred to as a parameter string, e.g. ~1 indicates that the data of parameter 1 is to be used. Parameters 1 to 10 are additional parameters. The strings are stored in the fields:

Param_01: Parameter parsed in to the query strings. ... Param_10: Parameter parsed in to the query strings.

Each parameter has a description for display purpose only. This parameter is editable when designing the report. These descriptions are stored in the field’s Descript_01 to Descrip_10. Parameters are strings edited by the user (e.g. “abcdef”) or data selected via list boxes (e.g. a list of the reader names with the required selection made (not edited). The fields type_01 to type_10 indicate a string (equal to 1) or list (equal to 2) of each parameter. When a list, the fields LIST_01 to LIST_10 is set with a value which refer to the ref field in the LIST TABLE which indicates where data for the list box display is to be found and what data is to be used in the parameter. The table LIST provides referencing for list parameters and contains the following fields:

Reference: referenced to by LIST_01 to LIST_10 in the report. Description: description of the list. DBI_name: The ID of the DBI reference in the REPORT.SQL file.

7 REPORT DESIGN When designing a report, the REPORT DESIGN dialog menu is selected in Set-up / Report.


The following parameters are set: The Report name design to be displayed or edited is selected via the list box. Changing the name of the report is by editing the name when the list box is closed. The default output of the report is as Report to the display, the Windows default printer or to a file. When reporting to a file, the default file is set at the Report to File option and the Zip Type and Zip File Name set the zip options. The Report type is selected as log (event report), accumulation (attendance report) or to other (reports on data bases.) Crystal name is the path and file name (with extension .RTP) .of the Crystal Report files that are used to generate the report, for example C:\SOFTWIN\SOFTREP\READER.RPT. The Crystal report may require Crystal query parameters to be sent to it, with fixed and/or user selected parameters. Crystal uses these parameters to find the required data for the report and the format and syntax of the parameters must match that which is known by Crystal and the Crystal report. The SQL query string can contain variable parameters that are selected by the user. A typical string is (See SQL queries for details):

{log.type}=1 and ((~1={log.sysno}) or (~1=0)) and ((~2={log.xref}) or (~2=0)) Certain parameters are always sent to Crystal and the report must be set to know these parameters (referred to as formulas in Crystal), even if they are not used. The parameters are generally used on the report, indicating the selection made. These parameters are:

Sdate: The start date of the report. Edate: The end date of the report.


Stime: The start time of the report. Etime: The end time of the report. Swindow: The start time of the report for each day. Ewindow: The end time of the report for each day. Param?d: Description of the parameter 1 to 10 selectable by the user. Param?v: Parameter 1 to 10 selected by the user. Reference: The report number. RepName: The name of the report.

Additional query parameters can be set for log reports via the Log query string. When searching for data in the log files passing the time and date requirements, the additional query is also tested before the data is passed to the logging file. This improves the speed of the report generation. See SQL queries for details. To generate 1st in and last out reports require special words in the SQL string “MINIMUM” (finds 1st entry for the day), “MAXIMUM” (finds last entry for the day) or “MINMAX” (finds 1st and last entry for the day). The default Start time, date is set in the format hh:mm:ss and yyyy-mm-dd. The date can be set to default as an offset of today. Selecting today with no offset make the default date equal to the date of the report. The offset in the format yyyy-mm-dd is deducted off the date when the report is generated, for example to generate a report of yesterday, the offset if 0000-00-01 and for a month ago, 0000-01-00. Similar to the default start time, date, default End time, date is set. The default Time window for which the report for each day (within start and end times and dates) is generated, is set in the format hh:mm:ss. 00:00:00 to 24:00:00 sets the full day. A DESCRIPTION for each additional parameter that the user is required to select is entered. If a description is set, the parameter option is not displayed to the user. The parameter the user can select is either a STRING, LIST or Lookup. A string is a number or string entered, and a list provides a list box of options to be selected, e.g. a list of the reader names. When the parameter to be selected is from a list box, the LIST ID must be set. This is a list box of types of lists available. The list is generated from the list database, which is editable from the lists available are selected from data set in table REP_LIST in Report.mdb. The database contains the name viewed in the report design and a database reference to SQL information in the file SoftRep.SQL Current lists are:

Alarm Area group Area zone Asset Names Asset Event Building

Camera Campus Card Card cost group Card cost type Card events

Card status Card type CMaker Event Controller Counter Department

Event Equipment Guest type Input Item Item Group

Licenses No / Yes Output PC Names Product Random Type

Reader Room Room Type Time Group Union Vender

Visitor name Zone to_from

Selecting the Lookup option requires on of the LIST ID selections (above). The lookup option displays the list of all the options for the set list as shown below. All settings that are checked are automatically converted to a string list of reference numbers for the checked, separated by comma (e.g. 2,3). These string lists are used in SQL and Crystal queries (see below), e.g.

{card_data.dept} in [2,3] The set-up typically is {card_data.dept} in [~1] Not (xref in [2,3]) The set-up typically is Not (xref in [~1])

In the design of the report, selection of lookup enables the select button which shows the lookup dialogue above, adding in the default selection (note that the default list can be generate by editing the list (e.g. 1,5,6). The header name (Dept Exclude Setting) of the lookup dialogue is obtained from the parameter description.


Each optional parameter is set with DEFAULT DATA and is used in the report if the user does not change the selection.

7.1.1 SQL QUERY STRINGS Sequential Query Language (SQL) strings are used to filter data from database files. These are “English type” strings and vary slightly for filtering data from daily files (event, accumulation and audit) – referred to as Log query and for filtering data out of other data files – referred to as Crystal query. The log queries are filter data from the daily files and load the resultant data in the databases Logging.mdb, accume.mdb or audit.mdb (depends on the report type). Thereafter Crystal reports are called with the Crystal query string as a parameter. The differences between Crystal and Log queries are explained with the following examples:

Crystal: ({log.type}=1) and ((~1={log.sysno}) or (~1=0)) and ((~2={log.xref}) or (~2=0)) Log: and (type=1) and ((~1=sysno) or (~1=0))and((~2=xref) or (~2=0))

This sets to select data where the field “type” in the data table “log” is equal to 1 (thus only reader events) and the 1st parameter available to the operator (indicated with ~1) selection matches the data in the “sysno” field, (thus a specific reader selected) or the 1st parameter is set to 0 (thus any reader) and the 2nd parameter is equal to the card selected or any card (0 is selected). The value selected by the operator for the parameter is inserted into the string (e.g. the operator selects “Entry reader” which is reader 5, ~1 is replaced with 5). If the operator does not make a selection, the default setting (as set in the design and displayed) is replaced (generally 0). Queries are not case sensitive, i.e. upper and/or lower case letters can be used. Lower case is preferred as more data can be displayed when using long strings and upper case used to make lines more (easier) readable. The number of spaces is irrelevant and spaces are used to make lines more readable (at the expense of possibly not seeing the complete line without scrolling). As queries are limited to 255 characters, spaces may have to be limited. Spaces or brackets are required to separate operators (AND OR), e.g. and(type=1)or ~1=xref and(sysno=5). Hence spaces before of after brackets are irrelevant. Queries are test from the left and pass when the answer of the test is true. Brackets are used to group tests within the string, e.g.

(a=b)and((c=d)or(x=y)) If a=b is true and ((c=d is true)or(x=y is true)) the query is true. If a=b is false, the query is false. If a=b is true and c=d is true, the query is true, even if x=y is false, hence a must be equal to b and as (c=d)or(x=y) have brackets around ( ()or() ), at least one of the two must also be true. The word NOT changes true to false and false to true, e.g. (a=b)and not(c=d), hence a must be equal to b and c must not be equal to d. Crystal field names are defined in { } and is the table name dot field name. Log field names do not require the table name or brackets (the table is already known). The only field names that can be used event log queries are the fields in the log table in LOGGING.MDB, which are TIME, DATE, TYPE, SYSNO, XREF, VALUE, REF2, Z1 ..Z10 (depends on the log parameter settings. All are long integers. Similarity field names that can be used in log queries for accume and audit are the fields in the accume table in ACCUME.MDB and in table audit in AUDIT.MDB. Crystal field names can be any field name defined in the Crystal .rpt report file used. The log query string is appended to the SQL string automatically generated from the date and time parameters and hence the string must start with AND or OR. Syntax for set for Crystal queries is: in [x,y,z ], e.g.

{card_data.dept} in [1,2,4] dept must be equal to either 1 or 2 or 4. Syntax for set for SQL queries is: in (x,y,z ), e.g.

Not (xref in (1,2,4)) xref must not be equal to either 1 or 2 or 4.

Syntax for ranges in Crystal queries is: in (x to y ), e.g.

{card_data.dept} in (1 to 10) dept must be 1, or 2 or ….10 (between 1 and 10). Syntax for ranges in log queries is: between x and y, e.g.

Xref between 1 and 10) xref must be 1, or 2 or ….10 (between 1 and 10). #Combinations of sets and ranges can be used. As examples:

Find cards that are now on site – not in the off site zones 0,1,2,4 and not in zones 10 to 20. Zone 0 is included as card that have never been used are in site 0. Note the sections have been separated in to lines with and explanation per section and as they sections are separated by and, every section must be true:


({card_data.status}<>0)and Card must be enabled. Not({card_data.location} in (10 to 20))and Card must not be in area zones 10 to 20. Not({card_data.location} in [0,1,2,4])and Card must not be in area zones 0,1,2 or 4. ((~2=0)or({card_data.dept}=~2)) Card must belong to the department the operator selected

(department ignored if operator made no selection).

Find cards that are now on site – in zones 0,1,2,4 or in zones 10 to 20: ({card_data.status}<>0)and Card must be enabled. ( ({card_data.location} in (10 to 20))or Card must be in any area zone 10 to 20 or 1,2 or 4. ({card_data.location} in [0,1,2,4]) )and Note bracket around this and previous section, spaces for

readability. ((~2=0)or({card_data.dept}=~2)) Card must belong to the department the operator selected

(department ignored if operator made no selection). Normally card number is of type number, if string is required – number convert. To sort the data within a day, the SQL command ORDER BY fieldname can be added to the log query string. For example, to order by time, add the string ORDER BY TIME to the SQL string (starting with a space when adding to a string). Note that records are stored in the log file when received from the controllers and may not be in time sequence if the time in the controllers are incorrect or the Access program has not been running, or a controller has been off line.

7.1.2 NUMBER CONVERT Normally card number is of type number and reports are shipped expecting number. Should card number be of type string, the parameters for card number in Crystal queries must be changed. For example, when Dallas touch tags are used or when card numbers are more than 10 characters (can be 12 digits). Typically, for type number the crystal query is ((~1=0)or({card_data.card_num}=~1)), i.e. if card number 0 is selected, or if the card

number entered for the search matchers the number in the card database. For type string, the query must be: ((“~1”=”0”)or({card_data.card_num}=”~1”)) Reports that display a field that has been changed from number to string will not display any data in that column is the .RPT file has not been changed. This change is done via the program Seagate Crystal reports (not supplied by Softcon). Note that the report does run, the column simply contains no data. To change the .RPT, open with Crystal, delete the column (typically [CARD_NUM ]), select the function Database -> Verify Database (select yes to the update) and replace the column via the Insert -> Database Field function (click and drag the appropriate field to the column). When a field type change is made (e.g. number to string) and such a field is linked to field in another database in the .RTP (e.g. field CARD_NUM in table CARD_DATA in CARD.MDB is linked to field CD_NUM in table VISITOR in VISITOR.MDB), both fields must be of same type or a link error will be displayed when running the report. To change a field type, the SoftWin programs (including SCS_SERVER) must be stopped and the TYPE and SIZE setting in c:\SoftWin3\config\DATABASE.MDB, table FIELDS must be set appropriately for the appropriate field (e.g. TYPE is set to text, SIZE to 12 for F_CD_NUM). Restarting SCS_SERVER will change the field type in the appropriate table. Note that this will result in a loss of all data in that field – if data must be preserved, the field type must be changed via an appropriate program (e.g. Microsoft ACCESS) before running SCS_SERVER. Please contact the Softcon helpdesk if difficulties are experienced with number conversions.


8 SOFTREP EXECUTION

SCS_Report is a client program that links via TCP/IP to SCS_RepServer which must be running before SCS_Report is started. On starting SCS_Report, the PC network name of where SCS_RepServer is running must be entered, if on the same PC, the host name localhost can be used. The default user Administrator, password Admin has access to all functions. SCS_RepServer links to SCS_Server – transferring login, reports run and database information such as set-up data. The parameters when starting the programs are listed in the help about.

The parameters for SCS_RepServ /fetch, /sync and SCS_Report /start:host, /RepServ:host select different PC configurations. When running SCS_Server, SCS_RepServer on the same PC, none of these parameters are required. When running SCS_Servers on a different to SCS_Report, SCS_RepServ must run on the same PC. No parameters required. When using SCS_Reports that can only be linked to one another (one links to SCS_Server), a SCS_RepServ (with \,sync) must be run on the PC with SCS_Serv and the intermediate PC must have a SCS_RepServ (with \fetch). For example: /fetch copies the databases (SCS_RepServ on PC2) from PC1. /sync (SCS_RepServ on PC1) synchronizes databases on PC2. /Start:host selects where SCS_Server is running (e.g. /Start:PC1). /RepServ:host selects where SCS_RepServer is running (e.g. /RepServ:PC1).

PC3 SCS_Client

PC2 SCS_Client

SCS_RepServ /fetch:PC1

PC1 SCS_Server

SCS_RepServ /sync


New reports are run by selecting the new Icon or selecting new in the Report menu.

The desired report is selected by entering Report Reference number or selecting the report via the Report Name list.

The databases section is enabled when connecting to SCS_Server on another PC. Databases are transferred to the local PC before reports are generated and selections are:

The Start Time/Date and End Time/Date sets the start and end of the log and accumulation (time is irrelevant) reports. The default for start and end dates can be designed to be today or today less year(s), month(s) and day(s). The Time Window is the time period with each day (log files only) for which the report must be generated. A window of 00:00:00 to 24:00:00 is set for all transactions. The Output of the report is selected to File (with the name of the file entered), to Printer (see Printing) or to Screen. The default selection is set via report design and changed by clicking on the required selection icon. If output is to screen, once


displayed, the operator can print or save to file.

When selecting directly to file, the Output File name, path and type can be selected by selecting the save as button as Microsoft Excel (.xls), Hypertext Markup Language (.html) or as Rich Text Format (.rtf). The default is html and file name if the report reference number _ date _ running number as indicated. The output file can optionally be zipped into one file or into a file per page (multiple zip files), with zip file name being set.

Additional parameters can be available for selection (if so designed). A Description indicating the parameter functions and Item, is the default selection that can be changed by selection of the list, or editing the search string. When Creating the report, the request is sent to SCS_RepServer which creates the report and exports to file(s) as set in the Settings menu. The default is the HTML format, with MS Excel and RTF formats optional. The location of these files can be selected, the default is c:\SoftWin3\Reports\?\??\, where ? is the report reference number and ?? the temporary file name ~newxxx. xxx starts at 001 and increments for each report window open (restarts at 001 when the 1st window of the report). Reports are created to a file per page and by default stored in a zipped file.

Pages of a report are displayed by entering the page number clicking in the 1st, previous, next or last page Icons repectively. (PgUp, PgDn to be added).

While the report is being generated, selecting the stop icon terminates the creation and displays the data found.

Allows for searching for data in the report.

Prints the report to the default printer.

A report can be Saved As a report with a new name – HTML zipped file, to be viewed and printed by SCS_Report when required. HTML, MSExcel and RTF file save formats can also be selected. Reports previously created and saved can be

Viewed by clicking and selecting the appropriate saved report.


Selecting Help About in the help menu (or starting SCS_Report with the parameter /?) displays the parameters available when starting SCS_Report. When starting the program via the exe events in SCS_Clients, the pn: values can use data in the event triggers, e.g. p1: ~x sends the xref field as the 1st parameter (See SCS_Client). /AF:filepath sets auto file create with path and file name. /FZ:x:filepath set zipping of the file, with path and file type of the zip file. x is one of the following:

x = 1 – single zip file x = 2 – multiple zip file x = 3 – single zip file, delete source file(s) (i.e. html, rtf, xls) x = 4 – multiple zip file, delete source file(s) (i.e. html, rtf, xls)

The /E: option sets an additional event to generated once the report has been generated (note that a report generated – with or with-out error event is generated and logged when a report is generated). The additional event is set in quotes, e.g. /E:”t1 n5 s123 z11234” – with parameter not given, defaulting to 0 (thus t1 n5 s123 x0 v0 a0 z11234 z20). Such optional events are typically used to trigger k#email of the report (see SCS_email). To run reports on the occurrence of events, e.g. print a slip of a card when the card is presented at a reader, the following needs to be set:

1. Create the required report, e.g. report 38: sw3_card_clock-in_slip.rpt 2. Set an exe event, e.g.


LogOn/Off: Menu options are in accordance with the PASSWORD entered, which is changed by logging on with a new password. Log on / off defaults to the lowest level password.

The Window menu allows for Cascade, Tile vertical, Tile horizontal of multiple report display and to Arrange Icons of minimised windows of reports. Help provides a link to this help document.


9 PRINTING Printing requires the System Printers and Report Printers to be set:

9.1 PRINTERS (system) Sets the printers in the system and allocates the Windows Name of the printer and the number of Slip Copies the printer on POS must print on a sale. Printer Name is a name to identify the printer in lists (e.g. in Report Printer). PC selects the PC using the printer. All applications on this PC can use this printer. Each PC using a printer must be entered – same windows name, different printer name and PC:

9.2 REPORT PRINTERS Sets which printers reports use. Printers selects the appropriate printer (defined in the system printer’s menu above) and Reports select the specific report or all. If it is required to print a report on more than one printer, add an extra line, with the appropriate printer, same report. Selection of all reports enables the printer for all. Note that if password allows, the printer selection can be changes when running a report.

In the example, when running report 4 (not Card database – Laptop) the option available are to print on printer 1 and 2.

Selecting << allows the selection of enabled printers by checking the printer. Note that all system printers are shown, only printers enabled for the report can be selected (others are faded). The report will print on all selected printers.


10 STANDARD REPORTS Listed below are reports shipped as standard. The default for all log reports set with a time window of 24 hours, for the current day. Accumulation reports do not use time settings, with the default date of yesterday. Accumulation requires that clock in and out readers, and end of day, week and month have been configured. Reports are generated only for dates that have passed the end of day time, e.g. if the end of day is at 20h00, the report for the day can only be generated after 20h00 on that day, thereafter at any time. When name is logged in the log files (special setting in ACCESS.CFG) and the cardholders name is retrieved from the log file, special .rpt files are required (e.g. reader_l_name.rpt). The searching for name also requires that the name be compared from the log file. This requires the SQL setting of (assuming only reader data is required, i.e. type=1 and that parameter 1 is name of type string with no default, i.e. no data, not even a space and parameter 2 is reader or type list): and(type=1)and((~2=0)or(~2=sysno))and(name like ''~1%'')

note that two single quotes precede ~1% and is followed by two single quotes. The % selects wild characters, e.g. selecting smi will result in all names starting in smi, i.e. smit and smith.

In certain installations it may be required that card number is a string (normally type number) - see number convert.

10.1 Accumulation

10.1.1 Accumulation - totals by card An accumulation report, listing the daily totals for the selected card (or all cards). The report uses Crystal Report c:\softwin\database\sw3_acc_tot.rpt, with the Crystal query: (~1=0)or({ACLOG.CARD_NO} = ~1).

The card is selected from a list box, default of all. The number of persons and the total day, week and monthly totals are listed per day, with grand totals for the report.

10.1.2 Accumulation - totals by department Identical to the totals report by card, but for a selected department, or all (equal to by all cards). The report uses Crystal Report c:\softwin\database\sw3_acc_tot.rpt, with the Crystal query: (~1=0)or({card_data.dept}=~1).

The report is ordered by department.

10.1.3 Accumulation - by card An accumulation report, listing the accumulation per selected card (or all cards). The report uses Crystal Report c:\softwin\database\sw3_acc.rpt, with the Crystal query: (~1=0)or({ACLOG.CARD_NO} =~1).

10.1.4 Accumulation - by department Identical to the accumulation report by card, but for a selected department, or all (equal to by all cards). The report uses Crystal Report c:\softwin\database\sw3_acc_dept.rpt, with the Crystal query: (~1=0)or({card_data.dept}=~1).

Grand totals per day and for the report are generated.

10.1.5 Accumulation week - by card An accumulation report, listing the week accumulation per selected card (or all cards) and selection of departments. The week minutes set per card for leave and required are displayed, with the difference calculated (accumulated week less required, less leave). The result is negative if accumulated plus leave is less than required. This report is run on the end of week accumulation. The report uses Crystal Report c:\softwin\database\sw3_acc_week.rpt, with the Crystal query:

((~1=0)or({aclog.card_no} =~1))and({card_data.dept}in ~2). Department number selections must be entered in square brackets, e.g. [1,4,5], or as a range round brackets, e.g. (1 to 10). The department selection must not be left blank.

10.1.6 Accumulation week - by department Identical to accumulation week – by card, with a selection of departments only, with totals per department. The report uses Crystal Report c:\softwin\database\sw3_acc_dept_week.rpt, with the Crystal query:

((~1=0)or({card_data.dept}in ~1).


10.1.7 Accumulation week - by card, page Identical to accumulation week – by card, with each department printed on a new page. The report uses Crystal Report c:\softwin\database\sw3_acc_cp_week.rpt, with the Crystal query:

((~1=0) or ({aclog.card_no} = ~1))and({card_data.dept}in ~2).

10.1.8 Accumulation week - by department, card An accumulation report, listing the accumulation per selected department (or all). The report uses Crystal Report c:\softwin\database\sw3_acc_card.rpt, with the Crystal query: ((~1=0) or {card_data.dept}= ~2).

Lists the department totals and the card daily totals.

10.1.9 Attendance (event 1st, last) - by date, dept, card A reader event report, listing the attendance per selected department or card (or all). The report uses Crystal Report c:\softwin\database\sw3_ev_rd_attend.rpt. The parameters are department, card, department exclude and reader. The Crystal

and SQL queries: ((~1=0)or({ card_data.dept}=~1))and not({ card_data.dept}in [~3]) MINMAX and(type=1)and((0 in(~4))or(sysno in[~4]))and((~2=0)or(xref=~2))order by xref. When only one reader event for a card is logged for a day, the report cannot discern first or last movement. The calculated attendance is shown in RED and if the event is before 12:00, last movement is assumes (i.e. attendance is equal to the time of the event) and if after 12:00, fist movement is assumed (i.e. attendance is equal to 24:00 less the time of the event). Note that similarly the same problem exists if a car moves though a number of readers after midnight before exit (attendance not shown in red). This problem can be eliminated by correct selection of readers in the set-up (readers only that are used for attendance entry and exit).

10.1.10 Accumulation – total min left by card Time (hh:mm) remaining for each card. The report uses Crystal Report c:\softwin\database\sw3_acc_minleft.rpt, with the Crystal

query: ((~1=0)or({aclog.card_no}=~1)) and ({@left}>0)and({@>}=True). Select card and set total time required to work and >minutes remaining to get to this total – e.g. total required is 8 hours per day and show card that are more than 10 minutes short of this total.

10.2 Card data Database reports of card set-up. Report start and end dates, times and windows are irrelevant. Unless indicated to the contrary, data is listed in reference order.

10.2.1 Card database – Cards by AreaG, last used date Crystal Report c:\softwin\database\sw3_ag_lst_used.rpt, with the Crystal query:

({card_data.reference }>0)and((~2=-1)or(~2={card_data.status}))and((~1=0)or(~1={card_data.area_grp})). The card can be selected from Area Group and status.

10.2.2 Card database – by Dept not Expired, total Crystal Report c:\softwin\database\sw3_card_tot_not_expire.rpt, with the Crystal query: ([~1]={Dept_data.reference}).

The card can be selected from Department.

10.2.3 Card database – by Dept, Expired Crystal Report c:\softwin\database\sw3_card_dept3.rpt, with the Crystal query:

({ card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and(([~2]=0)or([~2]={card_data.dept}))and((~3=-1)or(~3={card_data.status}))and (({@Daysx}>=0)). The card can be selected from Card, department and status.

10.2.4 Card database – by Dept, Not Expired Crystal Report c:\softwin\database\sw3_card_dept2.rpt, with the Crystal query:

({ card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and(([~2]=0)or([~2]={card_data.dept}))and((~3=-1)or (~3={card_data.status}))and(({@Daysx}<0)). The card can be selected from Card, department and status.

10.2.5 Card database – licences Crystal Report c:\softwin\database\sw3_card_licences.rpt, with the Crystal query:


({ card_data.reference}>0)and((~1=-1)or(~1={card_data.status}))and((~8=0)or({card_data.lic_1_type}=~8)or ({card_data.lic_2_type}=~8)or({card_data.lic_3_type}=~8)or({card_data.lic_4_type}=~8)or({card_data.lic_5_type}=~8)or ({card_data.lic_6_type}=~8)). The card status can be selected from a list of All, disabled, enabled or capture. The licenses to be checked (yes) and the specific licence type are selected from a list.

10.2.6 Card database – by ref number Crystal Report c:\softwin\database\sw3_card_num.rpt, with the Crystal query:

({card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and((~2=-1)or(~2={card_data.status})). The specific card is selected by entering the xref number. The card status can be selected from a list of All, disabled, enabled or capture.

10.2.7 Card database - by name Crystal Report c:\softwin\database\sw3_card_num.rpt, with the Crystal query:

({card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and((~2=-1)or(~2={card_data.status})). The specific card is selected from the list box of cardholder names. The card status can be selected.

10.2.8 Card database - by range Crystal Report c:\softwin\database\sw3_card_num.rpt, with the Crystal query:

({ card_data.reference }>0)and(({ card_data.reference }>~1)and({ card_data.reference }<~2))and ((~3=-1)or(~3={card_data.status})). The range of cards are selected by entering the first and last card reference numbers. The card status can be selected.

10.2.9 Card database - by card number Crystal Report c:\softwin\database\sw3_card_num.rpt, with the Crystal query:

((~1=0)or({ card_data.card_num }=~1))and({ card_data.reference }>0)and((~2=-1)or(~2={card_data.status})). The specific card number is selected by entering the card number. The card status can be selected.

10.2.10 Card database - alphabetically Crystal Report c:\softwin\database\sw3_card_alph.rpt, with the Crystal query:

({ card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and((~2=-1)or(~2={card_data.status})). The specific card is selected from the list box of cardholder names. The card status can be selected. Data is displayed alphabetically.

10.2.11 Card database - by employ Crystal Report c:\softwin\database\sw3_card_emp.rpt, with the Crystal query:

((~2=-1)or({card_data.status}=~2))and((("~1"="0")and(NumericText({card_data.employ})))or (UpperCase({card_data.employ}) like UpperCase("~1*"))). The employee number is entered (if all characters are not entered, all partial matches are listed. The card status can be selected.

10.2.12 Card database - by ref, name, surname Crystal Report c:\softwin\database\sw3_card_first.rpt, with the Crystal query:

({card_data.reference}>0)and(({card_data.reference}=~1)or(~1=0))and((~2=-1)or(~2={card_data.status})). The specific card is selected from the list box of cardholder names. The card status can be selected.

10.2.13 Card database - by time group Crystal Report c:\softwin\database\sw3_card_tg.rpt, with the Crystal query:

({ card_data.reference}>0)and((~2=-1)or(~2={card_data.status}))and((~1=0)or(~1={card_data.time_grp})). The specific cards are selected from the list box of time groups. The card status can be selected.

10.2.14 Card database - phones Crystal Report c:\softwin\database\sw3_card_phone.rpt, with the Crystal query:

((~1=0)or(~1={card_data.reference}))and((~2=-1)or({card_data.status}=~2))and((~3=0)or(~3={card_data.dept})). The specific card is selected from the list box of cardholder names or a specific department is selected from a list. The card status can be selected.

10.2.15 Card database - by department Data is listed ordered by department. Crystal Report c:\softwin\database\sw3_card_dept.rpt, with the Crystal query:

({card_data.reference}>0)and(({card_data.reference}=~1)or(~1=0))and((~2=0)or(~2={card_data.dept}))and


((~3=-1)or(~3={card_data.status})). The specific card is selected from the list box of cardholder names or a specific department is selected from a list. The card status can be selected.

10.2.16 Card database - by department, with company Data is listed ordered by department. Crystal Report c:\softwin\database\sw3_card_company.rpt, with the Crystal query:

({ card_data.reference }>0)and(({ card_data.reference }=~1)or(~1=0))and((~2=0)or(~2={card_data.dept}))and ((~3=-1)or(~3={card_data.status})). The specific card is selected from the list box of cardholder names or a specific department is selected from a list. The card status can be selected.

10.2.17 Card database - by dept area group Data is listed ordered by department. Crystal Report c:\softwin\database\ sw3_card_dept_ag.rpt, with the Crystal query:

({card_data.reference}>0)and(({card_data.reference}=~1)or(~1=0))and((~2=0)or(~2={card_data.dept}))and ((~3=-1)or(~3={card_data.status})). The specific card is selected from the list box of cardholder names or a specific department is selected from a list. The card status can be selected.

10.2.18 Card database - by area group Data is listed ordered by card name and area zone. Crystal Report c:\softwin\database\sw3_card_zn.rpt, with the Crystal query:

({card_data.reference}>0)and((~2=-1)or(~2={card_data.status}))and((~1=0)or(~1={card_data.area_grp})). The area group is selected from a list box. The card status can be selected.

10.2.19 Card database – Not used for # days from date Data is listed ordered by card name and area zone. Crystal Report c:\softwin\database\sw3_numdaysu.rpt, with the Crystal

query: (({@Numdays2}>=~1))and((~2=0)or({card_data.status}=~2))and((~3=0)or({card_data.dept}=~3))and((~4=0)or({card_data.Union}=~4)). The card status, department, Union and the number of days can be selected.

10.2.20 Cards allowed into an area Data is listed ordered by card name and area zone. Crystal Report c:\softwin\database\sw3_card_zn.rpt, with the Crystal query:

({card_data.reference}>0)and ((~2=-1)or(~2={card_data.status}))and ((~1=0)or({area_zone_group.area_zn}=~1))and ((~3=0)or (~3={card_data.dept}))and (((~5=0)and(~6=0))or(~5={card_data.reference})or({ card_data.card_num }=~6)). The cards are selected from the list box of cardholder names, a specific department, a specific area zone, the card number can be entered. The card status can be selected. Data entered for parameter 4 is displayed on the report heading.

10.2.21 Cards allowed into an area, dept Data is listed ordered by department, card name. Crystal Report c:\softwin\database\sw3_card_znd.rpt, with the Crystal query:

({card_data.reference}>0)and((~2=-1)or(~2={card_data.status}))and((~1=0)or({area_zone_group.area_zn}=~1)) and((~3=0)or(~3={card_data.dept})). The data can be selected from a list of area zone and a specific department. The card status can be selected.

10.2.22 Cards allowed into an area, dept, registration Data is listed ordered by department, card name. Crystal Report c:\softwin\database\sw3_card_area.rpt, with the Crystal query:

({card_data.reference }>0)and((~2=-1)or(~2={card_data.status}))and((~1=0)or({area_zone_group.area_zn}=~1))and ((~3=0)or(~3={card_data.dept}))and((~5=0)or(~5={card_data.reference}))and((~6=0)or(ToNumber({card_data.card_num})=~6)). The data can be selected from a list of area zone and a specific department. The card status can be selected.

10.2.23 Cards allowed into an area MultiGroups Data is listed ordered by department, card name. Crystal Report c:\softwin\database\sw3_card_zn_multiGr.rpt, or

sw3_card_ag_multi.rpt (only shows multi groups) with the Crystal query: ({ card_data.reference }>0)and((~2=-1)or(~2={card_data.status})) and((~3=0)or(~3={card_data.dept}))and ((~5=0)or(~5={card_data.reference}))and((~6=0)or(ToNumber({card_data.card_num})=~6)). The data can be selected from a list of area zone and a specific department. The card status can be selected.


10.2.24 Card database - by subsidy-alpha Data is listed ordered by card name. Crystal Report c:\softwin\database\sw3_card_sub.rpt, with the Crystal query:

({card_data.subsy_remain>0)and({card_data.reference}>0)and(({card_data.reference}=~1)or(~1=0))and ((~2=-1)or(~2={card_data.status})). A specific card can be selected from a list of card names. The card status can be selected. Only cards with a subsidy remaining are listed.

10.2.25 Card database - Credit Crystal Report c:\softwin\database\sw3_card_credit.rpt, with the Crystal query:

((~2=0)or({card_data.dept}=~2))and((~3=-1)or({card_data.status}=~3))and ({ card_data.value_remain}<>0)and((~1=0)or(~1={card_data.reference})). Card are selected by lists of department and card name. The card status can be selected. Only cards with a value remaining are listed.

10.2.26 Card database - Laptop Crystal Report c:\softwin\database\sw3_card_laptop.rpt, with the Crystal query:

((~2=-1)or({card_data.status}=~2))and((~1=0)or(~1={card_data.reference}))and Not(IsNull({card_data.car_regis}))and (("~3"="0")or(UpperCase({card_data.car_regis}) like UpperCase("~3*")))and(("~4"="0")or {card_data.car_descr} like "~4*"). Card are selected by lists of card name or entering laptop name or number (in caps). The card status can be selected. Only cards with a laptop names are listed. Note that Car registration is used as laptop name and Car description as serial number.

10.2.27 Card database – Finger Print Crystal Report c:\softwin\database\sw3_card_fp.rpt, with the Crystal query:

(({fp_cards.quality1}>0)or({fp_cards.quality2}>0))and(({ card_data.reference }=~1)or(~1=0))and ((~2=0)or(~2={card_data.dept}))and((~3=-1)or(~3={card_data.status}))and ((~4=0)or(ToNumber({fp_cards.quality1})<~4)or(ToNumber({fp_cards.quality2})<~4)) Card are selected by lists of card name or department or entering laptop name or number (in caps). The card status can be selected and a quality of the finger print set (0 is all, a value set displays only cards with a lesser quality). Only cards with a quality are displayed

10.2.28 Cards clock-in slip Crystal Report c:\softwin\database\sw3_card_clock-in_slip.rpt, with the Crystal query of:

~1={ card_data.reference}. The card is selectable by list. This report is typically started by an exe event that runs on card event at reader, e.g. c:\softwin\softrep\softrep.exe 38 p1:~x NP AP AS (passes report 38, xref as parameter 1 and set NoPrompt, AutoPrint and AutoStop).

10.2.29 Visitor database – issued Crystal Report c:\softwin\database\sw3_visitor.rpt, with the Crystal query: ({visitor.reference}>0).

Selects visitor card with an issue date/time greater than the start date/time and less than the end start/time.

10.3 Events These logged event use start and end times for selection, with additional SQL selection (selection from the daily log files to logging.mdb) and Crystal selections (logging.mdb linked to other data files). Reader event selection options include card type of all, card holders or visitor cards and event type of all, out-area, out-time, entered, disabled, expired or APB error. Card and department names in reports are referenced via the field ref2 in the log file from the visitor database when ref2 is not zero.

10.3.1 All events Crystal Report c:\softwin\database\sw3_ev_all.rpt, with the SQL query: order by time.

10.3.2 User log-on Crystal Report c:\softwin\database\sw3_ev_all_log.rpt, with the SQL query:

and ((~1=0)or(xref=~1))and (status in(148,146,147)).


10.3.3 Cards Area To week day / month / year tot Crystal Report c:\softwin\database\sw3_ev_year_tot.rpt, with the SQL and Crystal queries of:

and(type=1)and(status=22)and((~2=0)or(xref=~2)). ((~3=0)or({ card_data.dept}=~3))and((~4=0)or({ reader_status.aera_to}=~4)).

10.3.4 Cards number Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL and Crystal queries of:

and((~6=0)or(~6=xref))and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by date ((~2=0)or(“~2”={card_data.card_num}))and((~3=0)or(({log.ref2}=0)and ({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3))). The reader and department are selectable by list, the card by card number. Event and card type can be selected. Card reference number can be entered.

10.3.5 Cards name Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL and Crystal queries of:

and((~6=0)or(~6=xref))and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by date (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Event and card type can be selected. Card reference number can be entered.

10.3.6 Cards name in log Crystal Report c:\softwin\database\sw3_ev_rd_log.rpt, with the SQL and Crystal query of:

and(type=1)and((~2=0)or(~2=sysno))and(name like '~1%') . ((~2=0)or(“~2”={card_data.card_num}))and((~3=0)or(({log.ref2}=0) and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3))). The reader is selectable by list. The card name is entered.

10.3.7 Cards in/from area zone Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL and Crystal queries of:

and(type=1)and((~7=0)or(status=~7))and((~2=0)or(xref=~2))and((~4=0)or((~4=1)and(ref2=0))or((~4=2)and (ref2>0)))order by date. ((~6=0)or("~6"={card_data.employ}))and((~3=0)or(({log.ref2}=0)and({card_data.dept}=~3))or(({log.ref2}<>0)and ({visitor.dept}=~3)))and((~1=0)or((~1={reader_status.aera_to})and(~5<>2))or((~1={reader_status.area_in})and (~5<>1))). The reader, card and department and the zone name is selectable by list. Employee number can be entered. Event and card type can be selected.

10.3.8 Cards clocked for selected period Crystal Report c:\softwin\database\sw3_card_clocked.rpt, with the SQL and Crystal queries of:

ORDER BY LOG.XREF ({card_data.reference}>0)and(({card_data.reference}=~1)or(~1=0))and((~2=-1)or(~2={card_data.status})). The card ref, status and department are selectable.

10.3.9 Cards sort dept-name Crystal Report c:\softwin\database\sw3_ev_rd_dep_name.rpt, with the SQL and Crystal queries of:

and(type=1)and((~4=0)or(status=~4))and((~1=0)or(sysno=~1))and((~2=0)or (xref=~2))order by date. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Card type can be selected.

10.3.10 Cards sort dept per page Crystal Report c:\softwin\database\sw3_ev_rd_dept_xref.rpt, with the SQL and Crystal queries of:

and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by date. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Event and card type can be selected.

10.3.11 Cards sort name Crystal Report c:\softwin\database\sw3_ev_rd_name.rpt, with the SQL and Crystal queries of:


and(type=1)and((~4=0)or(status=~4))and((~2=0)or(sysno=~2))and((~1=0)or (xref=~1))order by date. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Event type can be selected.

10.3.12 Cards dept totals Crystal Report c:\softwin\database\sw3_ev_rd_dept_totals.rpt, with the SQL and Crystal queries of:

and(type=1)and((~1=0)or(sysno=~1))and((~6=0)or(~6=status))and((~2=0)or(xref=~2))order by date. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. The minimum card and department totals can be set. Event type can be selected.

10.3.13 Cards day dept totals Crystal Report c:\softwin\database\sw3_ev_rd_dept_day_totals.rpt, with the SQL and Crystal queries of:

and(type=1)and((~4=0)or(status=~4))and((~2=0)or(sysno=~2))and((~1=0)or (xref=~1))order by date. (~3=0)or({ card_data.dept}=~3). The reader and department are selectable by list, the card by card number. Event type can be selected.

10.3.14 Cards name totals, sort dept-xref Crystal Report c:\softwin\database\sw3_ev_rd_dept_xref_tot.rpt, with the SQL and Crystal queries of:

and(type=1)and((~6=0)or(status=~6))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))order by date. (~3=0)or(({log.ref2}=0)and({card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. The minimum card and department totals can be set. Event type can be selected.

10.3.15 Cards in/from area, sort empl - entries Crystal Report c:\softwin\database\sw3_ev_rd_emp_detail_tot.rpt, with the SQL and Crystal queries of:

and(type=1)and((~7=0)or(status=~7))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by date. ((~6=0)or("~6"={card_data.employ}))and ((~3=0)or(({log.ref2}=0)and({card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)))and ((~1=0)or((~1={reader_status.aera_to})and(~5<>2))or((~1={reader_status.area_in})and(~5<>1))). The area zone, card, department, card type (enabled, capture, all), zone to/from/both are selectable by list. The employee number can be set. Event type can be selected.

10.3.16 Cards sort company - dept Crystal Report c:\softwin\database\sw3_ev_rd_dept_company.rpt, with the SQL and Crystal queries of:

and(type=1)and((~4=0)or(status=~4))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))order by date. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Event type can be selected.

10.3.17 Cards random search Crystal Report c:\softwin\database\sw3_ev_random.rpt, with the SQL query of:

and(type=3)and(xref>0)and((~1=0)or(value=~1))and((~2=0)or(~2=xref)) order by date. The card and random result (all/searched/not) are selectable by list.

10.3.18 Cards 1st in Lists the cards first movement for the day. Crystal Report c:\softwin\database\sw3_ev_rd_1st.rpt, with the SQL and Crystal

queries of: MINIMUM and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Movement later than time in minutes can be set (cards that first move was before this time are not displayed). Card and event type can be selected.

10.3.19 Cards last out Lists the cards last movement for the day. Crystal Report c:\softwin\database\sw3_ev_rd_last.rpt, with the SQL and Crystal

queries of: MAXIMUM and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Movement last before time in minutes can be set (cards that last move


was after this time are not displayed). Card and event type can be selected.

10.3.20 Cards 1st in, last out Lists the cards first and last movements for the day.Crystal Report c:\softwin\database\sw3_ev_rd_1st_last.rpt, with the SQL

and Crystal queries of: MINMAX and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Movement first after time in minutes can be set (cards that first move was before this time are not displayed) and movement last before time in minutes can be set (cards that last move was after this time are not displayed). Card and event type can be selected.

10.3.21 Cards 1st of day Lists the first movement for the day. Crystal Report c:\softwin\database\sw3_ev_rd_min.rpt, with the SQL and Crystal queries

of: MINIMUM and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. ((~3=0)or({ card_data.dept}=~3))and (not({ card_data.dept}in [~6])). The reader, card and department are selectable by list. Card and event type can be selected. Departments can be excluded by entering a list of department reference numbers separated by comma, e.g. 1,5,3

10.3.22 Cards last of day Lists the last movement for the day. Crystal Report c:\softwin\database\sw3_ev_rd_max.rpt, with the SQL and Crystal queries

of: MAXIMUM and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Card and event type can be selected. Departments can be excluded by entering a list of department reference numbers separated by comma, e.g. 1,5,3

10.3.23 Cards 1st of day, last of day Lists the first and last movements for the day. Crystal Report c:\softwin\database\sw3_ev_rd_min_max.rpt, with the SQL and

Crystal queries of: MINMAX and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Card and event type can be selected. Departments can be excluded by entering a list of department reference numbers separated by comma, e.g. 1,5,3.

10.3.24 Cards 1st of day (any reader, fixed dept) Lists the first movements for the day, any reader for a fixed list of departments. Crystal Report c:\softwin\database\sw3_ev_rd_1st_any.rpt, with the SQL and Crystal queries of:

MINIMUM and(type=1) and((~1=0)or(~1=status)) order by xref. ({log.ref2}=0)and({card_data.dept}in[1,2]). Event type can be selected. Departments are fixed (1 or 2), Change these are required.

10.3.25 Cards – 1st in before time, Last out after time Lists the first and last movements for the day – before and after selected time (the opposite is 1st and last above), any reader for a fixed list of departments. Crystal Report c:\softwin\database\sw3_ev_rd_Overtime.rpt, with the SQL and Crystal queries of:

MINMAX and(type=1)and((~5=0)or(status=~5))and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))and ((~4=0)or((~4=1)and(ref2=0))or((~4=2)and(ref2>0)))order by xref. (~3=0)or(({log.ref2}=0)and({ card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The reader, card and department are selectable by list. Card and event type can be selected. Departments can be excluded by entering a list of department reference numbers separated by comma, e.g. 1,5,3.

10.3.26 Cards visitors Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL queries of:

and(type=1)and((~3=0)or(status=~3))and(ref2<>0)and((~1=0)or(~1=sysno))and((~2=0)or(~2=ref2)). The reader and card are selectable by list. Event type can be selected.


10.3.27 Cards reader/zone/room/building/campus Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL and Crystal queries of:

and(type=1)and((~1=0)or(xref=~1))and((~4=0)or(sysno=~4))and((~9=0)or(status=~9))order by date. ((~2=0)or({card_data.dept}=~2))and((~3=0)or(~3={reader_status.aera_to}))and((~5=0)or(~5={reader_status.room})) and((~6=0)or(~6={room.room_type}))and((~7=0)or(~7={room.building}))and((~8=0)or(~8={building.campus})). The card, department and the zone name, reader, room, room type, building and campus is selectable by list. Event and card type can be selected.

10.3.28 Cards printed/programmed Crystal Report c:\softwin\database\sw3_ev_cm_print.rpt, with the SQL and Crystal queries of:

and(type=10)and((status=153)or(status=154))and((~1=0)or((~1=1)and(status=154))or((~1=2)and(status=153)))and ((~2=0)or(~2=sysno))and((~3=0)or(~3=xref))and((~4=0)or(~4=z1))order by date. card_data.dept}=~3))or(({log.ref2}<>0)and({visitor.dept}=~3)). The PC, card and operator reference numbers are entered (by list in future versions). Card type can be set as 153 (programmed) or 154 (printed).

10.3.29 Input status changes (select an input) Crystal Report c:\softwin\database\sw3_ev_in_evst.rpt, with the SQL query:

and(type=2)and(sysno=~1). Specific input is selected via a list box of input names. The logged changes and the current status are displayed.

10.3.30 Inputs by group Special report where inputs are set with a group number in level 5 timeout, selection is via this group setting. Crystal Report c:\softwin\database\sw3_ev_input.rpt, with the SQL and Crystal query:

and(type=2) order by date. {INPUT_STATUS.L5_TMOUT}=~1.

10.3.31 Inputs Crystal Report c:\softwin\database\ sw3_ev_input.rpt, with the SQL query:

and(type=2)and((~1 = 0)or(sysno=~1)) order by date. A specific input can be selected via a list box of input names.

10.3.32 Input linked to card, by card A log report of a card (or all) linked an input (or all). Such transactions require the set-up of events, linking the last card used at a reader to an input changing to a set level. For example, when a person swipes his card and uses a push button to activate an alarm, the card used at that reader is linked to the input as the card that activated the alarm. The report uses Crystal Report c:\softwin\database\ sw3_ev_in_card.rpt, with the SQL query:

and(type=2)and((~1=0)or(sysno=~1))and((~2=0)or(xref=~2))order by xref. The input and card are selected from lists.

10.3.33 Outputs A log report of output events, using Crystal Report c:\softwin\database\sw3_ev_output.rpt, with the SQL query:

and(type=3)and((~1=0)or(sysno=~1))order by date. A specific output can be selected via a list box of output names.

10.3.34 Counters A log report of counter events, using Crystal Report c:\softwin\database\sw3_ev_count.rpt, with the SQL query:

and(type=6)and((~1=0)or(sysno=~1))order by date. A specific counter can be selected via a list box of counter names.

10.3.35 Exceptions: all Crystal Report c:\softwin\database\sw3_ev_all.rpt, with the SQL query:

and((status in(20,21,24,25,29,30,31,33,34,35,39,44,45,70,71,1,2,3,145,146,147))or((status=50)and(alarm=2))).

10.3.36 Exceptions: system Crystal Report c:\softwin\database\sw3_ev_all.rpt, with the SQL query:

and ((~1=0)or(sysno=~1))and (status in(1,2,3,145,146,147)). A specific controller can be selected via a list.


10.3.37 Exceptions: access Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL query:

and(type=1)and((~1=0)or(~1=sysno))and((~2=0)or(~2=xref))and(status in(20,21,24,25,29,30,31,33,34,35,39,44,45)). A specific reader can be selected via a list.

10.3.38 Exceptions: inputs Crystal Report c:\softwin\database\sw3_ev_input.rpt, with the SQL query:

and(type=2)and((~1=0)or(~1=sysno))and(alarm=2). A specific input can be selected via a list.

10.3.39 Exceptions: Unknown Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL query:

and(type=1)and(status=35)and((~1=0)or(~1=sysno))and(xref=0)and((~2=0)or(~2=value)). A specific reader can be selected via a list and a specific card number can be entered.

10.3.40 Exceptions: wrong format/facility Crystal Report c:\softwin\database\sw3_ev_rd.rpt, with the SQL query:

and(type=1)and((status=44)or(status=45))and((~1=0)or(~1=sysno)). A specific counter can be selected via a list box of counter names.

10.4 PPOS Events 10.4.1 Entry Day Totals Crystal Report c:\softwin\database\sw3_PPOS_items_day.rpt, with the SQL query:

and(status=363)and(Z1>0)and((~1=0)or(~1=z1))and((~2=0)or(~2=xref))and((~3=0)or(~3=sysno))order by date. A specific item and operator can be selected via list and a specific PC can be entered.

10.4.2 Entry PC Totals Crystal Report c:\softwin\database\sw3_PPOS_PC_items.rpt, with the SQL query:


10.4.3 Entry Totals Crystal Report c:\softwin\database\sw3_PPOS_totals.rpt, with the SQL query:


10.4.4 Entry Details Crystal Report c:\softwin\database\sw3_PPOS_items.rpt, with the SQL query:


10.4.5 CashUp Day Totals Crystal Report c:\softwin\database\sw3_PPOS_cash_day.rpt, with the SQL query:

and(status=365)and(Z1>0)and((~1=0)or(~1=z1))and((~2=0)or(~2=xref))order by date. A specific operator can be selected via list and a specific PC can be entered.

10.4.6 Entry/CashUp Day Totals Crystal Report c:\softwin\database\sw3_PPOS_totals_day.rpt, with the SQL query:

and((status=363)or(status=365))and(Z1>0)and((~1=0)or(~1=z1))and((~2=0)or(~2=xref))and((~3=0)or(~3=sysno))order by date. A specific item and operator can be selected via list and a specific PC can be entered.

10.4.7 Entry/CashUp PC Totals Crystal Report c:\softwin\database\sw3_PPOS_totals_PC_day.rpt, with the SQL query:

and((status=363)or(status=365))and(Z1>0)and((~1=0)or(~1=z1))and((~2=0)or(~2=xref))and((~3=0)or(~3=sysno))order by dateA specific item and operator can be selected via list and a specific PC can be entered.


10.5 Vending Certain vending reports have card type selections of all, card group or cost group.

10.5.1 Vending Events – totals (Dept) Crystal Report c:\softwin\database\sw3_vd_ev_dept_tot.rpt, with the SQL and Crystal query:

and(status=355). ((~1=0)or(~1={vender.reference}))and(~2=0)or(({log.ref2}=0)and({ card_data.dept}=~2))or(({log.ref2}<>0)and({visitor.dept}=~2)). Department and vender can be selected via list.

10.5.2 Vending Events - totals Crystal Report c:\softwin\database\ sw3_vd_ev_day_tot.rpt, with the SQL and Crystal query:

and(status=355). ((~1=0)or(~1={vender.reference})). Vender can be selected via list.

10.5.3 Vending Events - vender Crystal Report c:\softwin\database\sw3_vd_ev_vender.rpt, with the SQL and Crystal query:

and(status=355)and((~2=0)or(~2=sysno)) . ((~1=0)or(~1={vender.reference})). Vender and item can be selected via list.

10.5.4 Vending Events - details Crystal Report c:\softwin\database\sw3_vd_ev.rpt, with the SQL and Crystal query:

and(type=12)and((~1=0)or(xref=~1))and((~7=0)or(sysno=~7))and((~6=0)or(z2>~6))order by date. ({items.subsidy}>=ToNumber(~5))and((~2=0)or({card_data.dept}=~2))and((~3=0)or({vender.reference}=~3))and ((~8=0)or({items.group}=~8)). Card, department, vender, cost group, item and item group can be selected via list. The minimum item subsidy and charged subsidy can be entered.

10.5.5 Vending Events – cash load Crystal Report c:\softwin\database\sw3_vd_ev_cash.rpt, with the SQL and Crystal query:

and(type=1)and(status=351)and((~1=0)or(xref=~1))and((~3=0)or(~3=sysno))and ((~4=0)or((~4=1)and(value=0))or((~4=2)and(value<>0)and((~5=0)or(value=~5)))) order by date. ((~2=0)or({ card_data.dept}=~2)). Card, department, reader, card type and cost group can be selected via list.

10.5.6 Vending Events – totals details dept Crystal Report c:\softwin\database\sw3_vd_ev_dept.trpt, with the SQL and Crystal query:

and (status=355)and((~3=0)or(~3=sysno))and(~4=0)or(z2>=~4)). ((~1=0)or(~1={vender.reference}))and(~2=0)or(({log.ref2}=0)and ({ card_data.dept}=~2))or(({log.ref2}<>0)and({visitor.dept}=~2)). Department, vender, item and the minimum event subsidy can be selected.

10.5.7 Vending Events – item totals Crystal Report c:\softwin\database\sw3_vd_ev_item_tot.rpt, with the SQL and Crystal query:

and(type=12)and(status=355)and((~1=0)or(xref=~1))and((~4=0)or(sysno=~4))and ((~5=0)or((~5=1)and(value=0))or((~5=2)and(value>0)))order by date. ((~2=0)or(~2={card_data.dept}))and((~3=0)or(~3={vender.reference}))and((~6=0)or(~6={items.group})). Card, department, vender, card type, item and item group can be selected via list.

10.5.8 Vending Events – card totals Crystal Report c:\softwin\database\sw3_vd_ev_card.rpt, with the SQL and Crystal query:

and (status=355)and((~5=0)or(~5=sysno))and((~1=0)or(~1=xref))and((~4=0)or(~4=xref)). ((~2=0)or({ card_data.employ }="~2"))and((~3=0)or({ card_data.card_num}=~3)) and ((~7=0) or(~7={vender.reference})) and ((~6=0)or(~6={items.group})). Reference, employee and card number can be entered. Card name, vender, item and item group can be selected via list.


10.5.9 Vending Events – item totals by group Crystal Report c:\softwin\database\ sw3_vd_ev_group_item_tot.rpt, with the SQL and Crystal query:

and(type=12)and(status=355)and((~1=0)or(xref=~1))and((~4=0)or(sysno=~4))and ((~5=0)or((~5=1)and(value=0))or((~5=2)and(value>0)))order by date. ((~2=0)or(~2={card_data.dept}))and((~3=0)or(~3={vender.reference}))and((~6=0)or(~6={items.group})). Card, department, vender, card type, item and item group can be selected via list.

10.5.10 Vending Events – PC cash load Crystal Report c:\softwin\database\sw3_vd_ev_cash.rpt, with the SQL and Crystal query:

and(type=10)and(status=350)and((~1=0)or(xref=~1))and((~3=0)or(~3=sysno))and ((~4=0)or((~4=1)and(value=0))or((~4=2)and(value<>0)and((~5=0)or(value=~5)))) order by date. ((~2=0)or({ card_data.dept}=~2)). Card, department, reader, card type and cost group can be selected via list.

10.5.11 Vending Setup item totals Reports from the items database, the quantity of items vend and value thereof, Crystal Report c:\softwin\database\sw3_vd_set_item.rpt, with the SQL and Crystal query:

and(status=355). ({items.reference}>0)and not({items.name} like z*")and({items.subsidy}>=ToNumber(~1))and ((ToNumber(~2)=0)or({items.now}>ToNumber(~2)))and((ToNumber(~3)=0)or({items.total}>ToNumber(~3))). Item subsidy, now quantity and total quantity minimum values can be entered.

10.6 Set-up 10.6.1 Set-up Area group Crystal Report c:\softwin\database\sw3_set_area_group.rpt, with the Crystal query:

({area_group.reference}=~1)or(~1=0). An area group can be selected from a list.

10.6.2 Set-up Controllers Crystal Report c:\softwin\database\sw3_set_cntrl.rpt, with the Crystal query:

({controller.reference}<>0)and((~1=0)or(~1={controller.reference}))and({controller.type}<>0). A controller can be selected from a list.

10.6.3 Set-up CR351 Crystal Report c:\softwin\database\sw3_set_cr351.rpt, with the Crystal query:

({cr351.reference}<>0)and((~1={cr351.reference})or(~1=0)). A controller can be selected from a list.

10.6.4 Set-up Event Crystal Report c:\softwin\database\sw3_set_event.rpt, with the Crystal query:

{event.reference}=~1. An event can be selected from a list.

10.6.5 Set-up Inputs Crystal Report c:\softwin\database\sw3_set_input.rpt, with the Crystal query:

({input_status.display}>0)and({input_status.reference}<>0)and((~1={input_status.reference})or(~1=0))and ((~2=0)or(~2={input_status.cntr}))and({controller.type}>0). An input or a controller can be selected from lists.

10.6.6 Set-up Outputs Crystal Report c:\softwin\database\sw3_set_output.rpt, with the Crystal query:

({output_status.reference}<>0)and((~1={output_status.reference})or(~1=0))and((~2=0)or(~2={output_status.cntr}))and({controller.type}>0). An output or a controller can be selected from lists.


10.6.7 Set-up Readers Crystal Report c:\softwin\database\sw3_set_read.rpt, with the Crystal query:

({reader_status.reference}<>0)and((~1={reader_status.reference})or(~1=0))and((~2=0)or(~2={reader_status.cntr}))and({controller.type}>0). A reader or a controller can be selected from lists.

10.6.8 Set-up Ins name, levels List of input names with now statuses and level names. Crystal Report c:\softwin\database\sw3_set_ins.rpt, with the Crystal

query: ({input_status.reference}<>0)and((~1={input_status.reference})or(~1=0))and((~2=0)or(~2={input_status.cntr}))and({controller.type}>0). An input or a controller can be selected from lists.

10.6.9 Set-up Outs name, levels List of output names, now statuses and level names. Crystal Report c:\softwin\database\sw3_set_outs.rpt, with the Crystal

query: ({output_status.reference}<>0)and((~1={output_status.reference})or(~1=0))and((~2=0)or(~2={output_status.cntr}))and({controller.type}>0). An output or a controller can be selected from lists.

10.6.10 Set-up User information User and use groups with dates of password last changes Crystal Report c:\softwin\database\sw3_password.rpt.

10.7 Status Certain status reports have alarm status options of unknown (ignore), alarm, not accepted or accepted. Card status options are all, disabled, enabled or capture.

10.7.1 Cards in area Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:

({card_data.status}<>0)and({card_data.location}<>0)and((~1=0)or({card_data.location}=~1))and ((~2=0)or(~2={card_data.dept})and((~3=0)or(~3={card_data.union})). The area zone, department and union are selected from a list. See SQL queries for examples.

10.7.2 Cards on site Reports the not disabled cards currently at location(s), not in certain zones. Crystal Report: c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:

({card_data.status}<>0)and(Not({card_data.location} in [0,1,2,4]))and((~1=0)or(~1={card_data.dept})and ((~2=0)or(~2={card_data.union})). This assumes that area zone 1,2 and 4 is off-site. Zone 0 is cards not used. Department and union are selected from lists. See SQL queries for examples.

10.7.3 Cards in area - slip Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc_slip.rpt, with Crystal query:

({card_data.status}<>0)and({card_data.location}<>0)and((~1=0)or({card_data.location}=~1))and ((~2=0)or(~2={card_data.dept})and((~3=0)or(~3={card_data.union})). The area zone, department and union are selected from a list.

10.7.4 Cards last used, by employ Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:

({card_data.reference}<>0)and((~2=-1)or({card_data.status}=~2))and(("~1"="")or(("~1"="0")and (NumericText({card_data.employ})))or(UpperCase({card_data.employ})like UpperCase("~1*"))). The employee number can be entered and the card statuses are selected from lists.


10.7.5 Cards last used, by employ, date Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:

({card_data.reference}<>0)and((~2=-1)or({card_data.status}=~2))and(("~1"="")or(("~1"="0")and (NumericText({card_data.employ})))or(UpperCase({card_data.employ})like UpperCase("~1*"))). The employee number can be entered and the card statuses are selected from lists.

10.7.6 Inputs order ref Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:

({input_status.display}>0)and({input_status.reference}>0)and((~1=0)or(~1={input_status.reference}))and ((~2=0)or({input_Status.cntr}=~2))and({controller.type}>0)and({input_status.stat_lev}>0)and ((~3=0)or(~3={input_Status.alarm_st})). The input, controller and alarm status are selected from a list.

10.7.7 Inputs order name Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:


10.7.8 Inputs order changed Generates a report of all not disabled cards currently in a certain area. Crystal Report c:\softwin\database\sw3_stat_card_loc.rpt, with Crystal query:


10.8 Audit Certain reports card status options of all, disabled, enabled or capture.

10.8.1 Audit Crystal Report c:\softwin\database\sw3_audit.rpt.

10.8.2 Audit - cards Crystal Report c:\softwin\database\sw3_audit.rpt, with the SQL query:

and (field like 'F_CD_%')and((~1=0)or(primary=~1))and((~2=-1)or((field='F_CD_STAT')and('~2'=old)))and ((~3=-1)or((field='F_CD_STAT')and('~3'=new))). A specific card, new and old status can be selected via lists.

10.8.3 Audit – area zone group Crystal Report c:\softwin\database\sw3_audit.rpt, with the SQL query:

and(((field='F_AZG_ref')and(type=3))or(field='F_AZG_ZONE'))and((~2=0)or(~2=criteria_2))and ((~1=0)or(~1=criteria_1)). A specific area group and area zone can be selected via lists.

10.8.4 Audit – cards area zone Crystal Report c:\softwin\database\sw3_audit_cardgroup.rpt, with the SQL query:

and(((field='F_AZG_ref')and(type=3))or(field='F_AZG_ZONE'))and((~2=0)or(~2=criteria_2))and ((~1=0)or(~1=criteria_1)). A specific card and area zone can be selected via lists.


10.8.5 Audit – cards disabled (by dept) Crystal Report c:\softwin\database\sw3_auditdept.rpt

Department can be selected via lists.

10.8.6 Audit – cards disabled (by operator) Crystal Report c:\softwin\database\sw3_auditop.rpt

Operator can be selected via lists.

10.9 Special Special reports are created as required.


11 STANDARD CRYSTAL REPORTS


#k

control services · scs_report.docx 2017-03-08 page 1 of 59 scs_report help version – 01.03.18...

Documents