$UDE in IDF and crash

Author: i2stiller@gmx.de (istiller)

Hi freaks I do some $UDE("compile",...)  in a simple form. After $UDE it seems all okay, but a few statments later, UnifAce will crash. Either on calling an ENTRY or leaving an ENTRY This happens only, when starting this form direct in the IDF. Running this form from additional menu works. Does anyone has/knows a similare behavior? And on the other hand, what "clean up" happens after additional menu to prevent the crash? @UnifAce:Maybe you can gives us a hint, what to do after $UDE to clean up the environment Wink Ingo

7 Comments

  1. BTW:

    $procReturnContext should contain a sublist with all "messages" incl. infos, warnings and errors Message frame after compiling: "Compile Form: 'LPER1503' Form: LPER1503 Phase 2: Model definitions Phase 3: Prep. structure Phase 4: Form definitions Phase 5: Background text Phase 6: Component variables Phase 7: Procs compilation Phase 8: Structure tables Phase 9: Descriptor Phase 10: Save form Compilation done: [info 2, warnings 1, errors 0]" $procReturnContext "Context=UDE compile·;InputComponents=1·;OutputComponents=1" If there are errors, I got DETAILS Very strange ... Confused Ingo


    Author: istiller (i2stiller@gmx.de)
  2. istiller said

    BTW:

    $procReturnContext should contain a sublist with all "messages" incl. infos, warnings and errors Message frame after compiling: "Compile Form: 'LPER1503' Form: LPER1503 Phase 2: Model definitions Phase 3: Prep. structure Phase 4: Form definitions Phase 5: Background text Phase 6: Component variables Phase 7: Procs compilation Phase 8: Structure tables Phase 9: Descriptor Phase 10: Save form Compilation done: [info 2, warnings 1, errors 0]" $procReturnContext "Context=UDE compile·;InputComponents=1·;OutputComponents=1" If there are errors, I got DETAILS Very strange ... Confused Ingo  

    You need to enable the information and warnings when compiling. By default only the errors are logged. Here's some info about how to use the compile sub-switches with $ude: > $ude("Compile"): using compile sub switches Hope this helps. Daniel


    Author: diseli (daniel.iseli@uniface.com)
  3. Strange UIL in $item("DETAILS",$procreturncontext) Confused
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity VER1150A.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity VER1150A.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity STATUS_ZEILE.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity STATUS_ZEILE.FAV_DATENBASIS not found.·;
    SEVERITY=Error·!·;ID=1112·!·;MESSAGE=Total Proc compile errors: 1.·;
    SEVERITY=Error·!·;ID=1112·!·;MESSAGE=Total Proc compile errors: 1.·;
    SEVERITY=Info·!·;ID=1301·!·;MESSAGE=Component variable "STATUS" is not referenced in the component.

    Most of the messages are listed double. And there is no item about the error, but two times the hint, that there are errors


    Author: istiller (i2stiller@gmx.de)
  4. diseli said You need to enable the information and warnings when compiling. By default only the errors are logged. Here's some info about how to use the compile sub-switches with $ude: > $ude("Compile"): using compile sub switches Hope this helps. Daniel  

    Mercy Daniel


    Author: istiller (i2stiller@gmx.de)
  5. diseli said You need to enable the information and warnings when compiling. By default only the errors are logged. Here's some info about how to use the compile sub-switches with $ude: > $ude("Compile"): using compile sub switches Hope this helps. Daniel  

     As Mark mentions  a) the description for setting of messagelevel are wrong:      Correct is:        0 gives you all information(Info,warning,error)        1 only warnings and errros        2 only errors  b) warning 1000 "Field xyz not found" will not be in the the DETAILS BTW: Exactly for "Field not found" I m searching in all components. So $UDE is not the solutionFrown Ingo


    Author: istiller (i2stiller@gmx.de)
  6. istiller said
    Strange UIL in $item("DETAILS",$procreturncontext) Confused
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity VER1150A.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity VER1150A.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity STATUS_ZEILE.FAV_DATENBASIS not found.·;
    SEVERITY=Warning·!·;ID=1076·!·;MESSAGE=Path to painted entity STATUS_ZEILE.FAV_DATENBASIS not found.·;
    SEVERITY=Error·!·;ID=1112·!·;MESSAGE=Total Proc compile errors: 1.·;
    SEVERITY=Error·!·;ID=1112·!·;MESSAGE=Total Proc compile errors: 1.·;
    SEVERITY=Info·!·;ID=1301·!·;MESSAGE=Component variable "STATUS" is not referenced in the component.
    Most of the messages are listed double.

    The described problem already was recognized as Issue 31206 ($UDE compile returns double amount of warnings, errors, and infos). This issue is until now unresolved. Sorry.


    Author: diseli (daniel.iseli@uniface.com)
  7. istiller said BTW: Exactly for "Field not found" I m searching in all components. So $UDE is not the solutionFrown Ingo  

    I've created Issue 31782 ($ude("compile") does not add all warnings/erros to $procReturnContext) for this problem.


    Author: diseli (daniel.iseli@uniface.com)