Skip to main content

Patch 10.4.02-022

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 PostgreSQL15 (U1.7) on SUSE Linux Enterprise 12.5 and 15.2 (LU7 and LU8)

Fixes

UNI-33045COM Call-Out: Importing Type Library produces garbled function names in output messages with 64-bit
UNI-32800The 'entry' snippet is no longer part of the Uniface defaults.
UNI-13434OCX with Shell.Explorer fails on 64-bits when extended triggers are used



UNI-33045  -  COM Call-Out: Importing Type Library produces garbled function names in output messages with 64-bit

Solution available in patch(es):      10.4.02-022

Description:

When importing type library information using the command line switch /sti with /mwr=com (for generating COM Call-Out signatures) then the output shows garbled function names when using 64-bit Uniface.

For example:

Executing the following IDE command line:

/sti /mwr=com /pid Word.Application

Then the output looks like this when using 64-bit Uniface:

ProgId  [Word.Application]
Library [Word]

CoClass          : Application
Message    : Using interface [U_APPLICATION]
Interface      : _Application
Warning    : Renamed to [U_APPLICATION]
Warning    : Function @D߯Œ, parameter result_ has an unknown HANDLE type VT_DISPATCH, please supply one
Warning    : Function ИUnŒ, parameter result_ has an unknown HANDLE type VT_DISPATCH, please supply one
[...]

When using 32-bit then the output looks like this:

ProgId  [Word.Application]
Library [Word]

CoClass          : Application
Message    : Using interface [U_APPLICATION]
Interface      : _Application
Warning    : Renamed to [U_APPLICATION]
Warning    : Function Parent, parameter result_ has an unknown HANDLE type VT_DISPATCH, please supply one
Warning    : Function WordBasic, parameter result_ has an unknown HANDLE type VT_DISPATCH, please supply one
[...]

The generated signatures are not affected by this issue.

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None

Notes:

This problem is solved.

Back to top



UNI-32800  -  The 'entry' snippet is no longer part of the Uniface defaults.

Solution available in patch(es):      10.4.02-022

Description:

With the introduction of the 'function' keyword the 'entry' snippet has been removed. Entries are still valid so the request is to re-introduce the entry snippet.

Environment:

+ Uniface version: 10.x
+ Platform: Windows

Workaround:

Entries can still be created manually.

Notes:

This problem is solved.

Note: you need to load the set of defaults manually in order to get the 'entry' snippet re-introduced.

Back to top



UNI-13434  -  OCX with Shell.Explorer fails on 64-bits when extended triggers are used

Solution available in patch(es):      10.4.02-022

Description:

When using an OCX container widget that has (e.g.) the Microsoft Web browser control (Shell.Explorer) embedded and the OCX properties "Use extended triggers" is enabled then using the OCX handle to navigate to a page, e.g. http://google.com:

$ocxhandle(OCX)->navigate("http://google.com", "", "", "", "")

Will cause the following error when using 64-bit Uniface:

'ICCDRV-COM-ERR Error with ICC system occurred, Windows exception 0xc0000005 (EXCEPTION_ACCESS_VIOLATION) occurred in external COM method "Navigate"'

And the content of the OCX remains empty.

When doing the same using 32-bit Uniface then the embedded control will navigate to the specified page and there is no error when an Extended trigger is called.

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None.

Notes:

This problem is solved.

Back to top



Be the first to reply!
Terms & ConditionsAccessibility statement