Skip to main content

Patch 10.3.03-021

Downloads

Product availability Matrix (PAM)
Downloads of this patch are available from the Rocket Customer Support Portal.
Further explanation can be found here.

Currencies

  • Add support for Db2 v11 on AIX 7.2 (RSH)

Fixes

UNI-29436*Sentinel redistributable tools should all be 64bit*
UNI-29133Filtering Entity and Project Palette objects in Resource Browser can give unexpected results
UNI-26631$number can return incorrect result when input is Struct
UNI-12114$setting: assigning an empty string to a registry value will be stored as "0"



UNI-29436  -  *Sentinel redistributable tools should all be 64bit*

Solution available in patch(es):      10.4.02-000, 10.3.03-021

Description:

By error some 32bit dll's were delivered instead.

Environment:

+ Uniface version: 10.x
+ Platforms: ALL

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-29133  -  Filtering Entity and Project Palette objects in Resource Browser can give unexpected results

Solution available in patch(es):      10.3.03-021, 10.4.02-001

Description:

Filtering (or searching for) objects in the Entity or Project Palette's Resource Browsers can give an unexpected result when there are no matches in the first 50 occurrences (or the maximum number of suggestions specified by the IDE logical UBAR_RESULTS_MAXHITS). The Resource Browser will display "1 results shown, more found" at the bottom but no results. Clicking "Show all" displays the correct information.

Environment:

+ Uniface version: 10.x
+ Platform: Windows

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-26631  -  $number can return incorrect result when input is Struct

Solution available in patch(es):      10.3.03-021, 10.4.02-001

Description:

When a Struct is used as input for $number then the result can be incorrect in case a non-English locale is used.

How to reproduce:
1. Consider the following code:

trigger detail
variables
struct V_STRUCT
numeric V_NUM
endvariables
$nlsformat = "nlslocale"
$nlslocale = "de_DE"
V_STRUCT->NUMBER = "8,3"
V_NUM = $number(V_STRUCT->NUMBER)
message/info $concat("V_NUM = ", V_NUM)
end
2. Create a form component with a command button that uses the above detail trigger code.
3. Compile and test the form
3. Press the button

Result: The info message will show the text "V_NUM = 8".
Expected: The message should say: "V_NUM = 8.3"

Environment:

+ Uniface Version : >= 9.5
+ Operating System : Any

Workaround:

Assign the value of the Struct to a string variable and use that with $number, or use string extraction/substitution with the Struct.

trigger detail
variables
struct V_STRUCT
numeric V_NUM
string V_TEXT
endvariables
$nlsformat = "nlslocale"
$nlslocale = "de_DE"
V_STRUCT->NUMBER = "8,3"
V_TEXT = V_STRUCT->NUMBER
V_NUM = $number(V_TEXT)
; Alternative (string extraction):
; V_NUM = $number(V_STRUCT->NUMBER[1])
; Or (string subtitution):
; V_NUM = $number("%%(V_STRUCT->NUMBER)%%%")
message/info $concat("V_NUM = ", V_NUM)
end

Notes:

This problem is solved.

Back to top



UNI-12114  -  $setting: assigning an empty string to a registry value will be stored as "0"

Solution available in patch(es):      10.3.03-021, 10.4.02-001

Description:

When an empty string is assigned to a value of a registry key then
$setting will store the string "0" instead of "".

Environment:

+ Uniface: Version 9.3 (and higher)
+ Operating System: All Windows versions
+ Database: DBMS independent

Workaround:

Instead of an empty string assign the following as (empty) value to a registry
key: $encode("USTRING", $decode("HEX", "00"))

E.g.

variables
string vString
endvariables

$setting("", "HKEY_LOCAL_MACHINE\SOFTWARE\Uniface\Uniface 9\MyRegData",
"REGDATA") = $encode("USTRING", $decode("HEX", "00"))
putmess $concat("Value of MyRegData = [", $setting("",
"HKEY_LOCAL_MACHINE\SOFTWARE\Uniface\Uniface 9\MyRegData", "REGDATA"), "]")

; Result: "Value of MyRegData = []"

Notes:

This problem is solved.

Back to top



Be the first to reply!
Terms & ConditionsAccessibility statement