4.3 Salesware .INI Settings Reference : Other .INI settings table : SalesEZ_System.INI settings table
 
SalesEZ_System.INI settings table
 
.INI file
Section
.INI Setting
Valid values
Default
Description
See also
SalesEZ.INI
[Data]
ODBC_DSN
Name of any valid SQL Server database
“” (empty string)
ODBC Data Source Name for live database. Data path form: If there is a database specified in the .INI file, it is added to the ODBC DSN in the display
 
Example:
ODBC_DSN=SiriusServer
Database=SiriusSQL_Training
would yield SiriusServer - SiriusSQL_Training
 
 
SalesEZ.INI
[Data]
Database
Name of any valid SQL Server database
Same name as the ODBC_DSN name.
Name of the SQL Server database. If it is not passed, defaults to the same name as the ODBC_DSN name.
 
ODBC_DSN
SalesEZ.INI
[Data]
Training_ODBC_DSN
Name of any valid SQL Server database
“” (empty string)
ODBC Data Source Name for training database. Training data path form.
 
 
SalesEZ.INI
[Data]
Training_Database
Name of any valid SQL Server database
Same name as the Training_ODBC_DSN name.
This is the name of the SQL Server training database. If it is not passed, defaults to the same name as the Training_ODBC_DSN name.
 
Training_ODBC_DSN
SalesEZ.INI
[Data]
ExceptionsPath
Any valid local path
 
Used to identify the path to Exceptions tables.
 
 
SalesEZ.INI
[Data]
NeverClose
TRUE/
FALSE, YES/NO, ON/OFF, 1/0
YES
Prevents the closure of non-essential tables after every call. Setting this to Yes gives a bit better performance.
 
 
SalesEZ.INI
[Prefs]
VerbosityLevel
Integer from 0 - 5
0
Level of logging application’s activities to the SalesEZ_log.txt file. Levels are from 0 to 5 (0=no logging, 5=full logging). Currently, all calls using MySQLexec() and TUpdate() are logged.
 
 
SalesEZ.INI
[Prefs]
MaxLogFileSize
Positive integer up to 16777184, representing bytes.
2000000
Allows an administrator to specify the maximum size, in bytes, of the salesez_log.txt file before it is truncated. Maximum size of this setting is 16777184 bytes, which is the physical limit of a character string in the EZ module.
 
 
SalesEZ.INI
[Prefs]
SQLEXECThreshold
Positive integer representing seconds
2
This allows you to set the number of seconds to wait for a query to complete before it logs the call to the SalesEZ_LongCallsAndErrors_log.txt file. This log file contains every MySQLexec() call that takes longer than the specified number of seconds and every MySQLexec() call that returns a server side error message.
 
 
SalesEZ.INI
[Prefs]
LogBadScans
TRUE/
FALSE, YES/NO, ON/OFF, 1/0
NO
If YES, activates the logging of bad scans to the BadScans_log.txt file. When a validation takes place on a number that does not exist in the system, or does not match in exception table lookups, this invalid scan can be optionally logged to the BadScans_log.txt file. This text file is a list of invalid scans, one per line. Each line contains the following comma delimited fields: Server DateTime, Scan (trickled) DateTime, Operator, Salespoint, Physical Location and Scan Number.
 
 
SalesEZ.INI
[Prefs]
EmbeddedSiteNo
TRUE/
FALSE, YES/NO, ON/OFF, 1/0
NO
If YES, all tnSiteNo parameters in CheckPass, ValidatePass, CheckAndValidatePass, TricklePass, CheckCard, ValidateCard, CheckAndValidateCard and TrickleCard default to the embedded site number in the pass number if tnSiteNo is not passed in. If NO, tnSiteNo defaults to prefs.site_no if tnSiteNo is not passed in.
 
 
SalesEZ.INI
[Prefs]
SQLEXECmaxrows
0 or positive integer
1000
Sets the maximum number of rows allowed to be returned from the server in any SQL SELECT statement. If this limit is exceeded, the error message, “Maximum number of rows retrieved from database exceeded. Limit is NNNN rows” error message is returned to the calling function and the offending SQL statement is logged in the LongCallsAndErrors_log.txt file. To disable this check, set this setting to 0.
 
 
SalesEZ.INI
[Prefs]
ScannedCardValidationPriority
TRUE/
FALSE, YES/NO, ON/OFF, 1/0
NO
If YES, gives the pass attached to the scanned card number first priority in the validation precedence list of passes that the guest owns. This is useful for situations where a guest owns more than one of the same pass DCI (such as a guest owning multiple discount value cards), and each of these passes allow a limited number of uses per day/week. This ensures that the pass attached to the scanned value card is the one that has validation attempted on it first.
 
 
SalesEZ.INI
[Prefs]
ScanIgnoreInterval
Positive integer representing seconds
 
SalesEZ application now ignores subsequent offline scans when they are trickled and fall into the interval set by the new SalesEZ.INI setting in [Preferences] ScanIgnoreInterval=3.5 (seconds, don't include parentheses and contents). When scans fall into the ScanIgnoreInterval the subsequent scans are marked in the corresponding gst/acc_actv table with active_type of 119 Scan Ignored - Pass# XXXXXXXXXX and Pass # XXXXXXXXXX is ignored because another scan found within ScanIgnoreInterval = 3.5000.