This setting specifies whether to log the instances when Dexterity decides which type of range to use for tables that use the SQL database type. The log will list all instances when Dexterity detected a range that was not “well-behaved” and whether Dexterity used an exclusive or inclusive range.
FHCheckRanges = option
• option - A boolean that indicates whether range logging is activated:
![[spacer]](1p.gif){kind=small}
|
Value |
Description |
|---|---|
|
TRUE |
Activates range logging, causing the FHRANGE.LOG text file to be generated in the same location as Dexterity or the runtime engine. |
|
FALSE |
Inactivates range logging. FALSE is the default. |
Under typical conditions, an inclusive range generated the c-tree Plus or Pervasive.SQL database managers and the exclusive range generated by the SQL Server database manager will contain the same records. But, because different rules are used to create the ranges, the possibility exists for the ranges to differ. Ranges that produce the same results for all database managers are considered “well-behaved.” These “well-behaved” ranges have the following characteristics:
|
It is desirable for a range to be “well-behaved” because “well-behaved” ranges produce the same results for all database managers. |
Every time a range end statement is executed for a SQL table, Dexterity examines the range conditions and decides which type of range to use for the table. If the range is “well-behaved” or Dexterity can alter the range to make it “well-behaved,” an exclusive range will be generated. Otherwise, an inclusive range will be generated. The FHRANGE.LOG file will list all instances when ranges for SQL tables were not “well-behaved” and whether Dexterity used an exclusive or inclusive range for the table. The log will not include ranges where the inclusive or exclusive option was used in the range end statement.
The following illustration shows the FHRANGE.LOG text file. Note that it specifies the table for which the range was not “well-behaved,” the type of range Dexterity used, and the script in which the range was set.
LogStarted: 2/6/96 9:19:24 AM FILE,SCRPT, FORM, TYPE, WARN,LINE TableName, Problem, Mode, Script Name * 22000,22002,22000,00002,00002,00006,"Purchase_Data", Nonmatching Sets, Full Inclusive! "Purchases_WIN_PRE on form Purchases"