Hello,

We install Uniface RunTilme 9.6 with MySQL Databses. At some customers, we have several schemas. Consequently, these customers have several shortcuts, one for each DataBase.

The differentiation between these schemas is made in .asn urtouer file. For schema1, we use :

[PATHS]
$MQL    MQL:MyServer:schema1|user|pwd
$DEF    $MQL

For schema2 we have :

[PATHS]
$MQL    MQL:MyServer:schema2|user|pwd
$DEF    $MQL

Sometimes, at these customers, we get $Status=-2 on read statment (record not found) and a few seconds later we get $Status=0 on the same record, as if, the first read was made on a "extra" schema.

Have you ever encountered this problem ?

Is there a statment to know the active database at a moment ?

Thanks for advance,

Regards.

... in addition,  I catch message log from debugger when the problem appears.

You can see in :

• "capture ok" the "Select" order which is succesful (hits selected 1),
• "capture nok 1" the "Select" order is not present, Uniface tries to access a strnage file in the \\sig directory,
• "capture nok 2", another type of error on .msg files.

Hope this can help.

Regards,

Hello,

I cannot really say much about the described error. I do not think that I have heard of such a problem before.

Regarding the message log I have the following remarks:

• "capture nok 1" the "Select" order is not present, Uniface tries to access a strnage file in the \\sig directory,
  Are you sure this is not something that is done in the application code? This looks like as if an activate is done for a component called "#ERREUR#". This, of course, will fail since this is not a valid component name. Or is there maybe some file mapping in the application ASN that could cause this? But this is not something that Uniface would do just by itself.
• "capture nok 2", another type of error on .msg files.
  This type of error message is not really unusual. It looks like the application is trying to load the date-time properties of a language setup. And I assume that you have set $language = "F" which would explain why it is searching for the messages with the language code F.

In case you are using $IOPRINT or /pri = 127 then you should see some details about the database when the driver does the logon. But Uniface 9.6 is very old, and I do not remember if it provides the same info as version 10.

I hope this helps.

Hi Daniel,

Thanks for your response.

You said : "Are you sure this is not something that is done in the application code?"

=> We have no ProcCode at this time in our application.

"Capture ok" and "Capture nok 1" are made in the same component at the same retrieve statment, so if our problem was due to bad code, we should have the problem each time, no ?

We will use /pri=127 to have much informations and I tell you the result.

Have a good day,

Regards,

Laurent.

Hi Daniel,

Here are some infos with /pri=127. It does not give much many more informations. Uniface always attempts to access a strange file within the retrieve.

What do you think of ?

Thanks for advance,

Laurent.