All posts by gianni

Long time Uniface happy user...

$dberror generalization

Doing database I/O when getting an error Uniface is providing $dberror to expose real database error captured from db connector, enabling to fine tune application error management.
There should be an equivalent function (or $dberror implementation should be generalized) exposing real error also for other connector types; as an example SOAP connector should expose HTTP transport error (See: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes).
As of U9.7 this fine tuning can only be partially implemented analyzing strings given back from connector into $procerrorcontext; string analysis could be prone to errors because of software evolution or different languages or possible customizations, while an errorcode is a much more simpler and stable information.

Uniface logical printer should become compatible with standard Microsoft printer redirection

A \”logical printer\” is an Uniface object collecting a specific subset of attributes (paper format, paper tray, ecc) for a Windows printer; it must be noted when a logical printer is saved from Uniface into the registry is including the printer name in its definition.

Printers redirection is a standard administration feature in a Windows environment enabling to remap local printers to be used from user session. When a printer is remapped for current user session its name is changed adding at the end a string like \” (remapped XXX)\”: Windows sysadmin while configuring printer redirection could decide XXX is current user or XXX is current user sessionID. Printer redirection is tipically used in a networked multisite environment.

As of today Uniface logical printers are NOT compatible with standard Microsoft printer redirection; there should be a way to remap original printer name saved from Uniface into registry to remapped printer name.