Load Fields-Problem

Author: amando.sanz@gmail.com (amando)

Problem whit Load Fields by creating a form, the length of the fields do not match the model defined in Uniface. Does anyone know why? Uniface 9.04.1 Greetings Amando

8 Comments

  1. Hi

    Can you give more info on the fields your want to load. The type, their length in the model, what you get, etc..

    I know that for string fields, when they exceed a certain length, Uniface limits the result.

    Kind regards,
    Richard


    Author: richard.gill (richard.gill@agfa.com)
  2. Hi Richard, Templates : String CPAIS >> C3 CPROVI >> C2 DPROVI >> C20 Kind regards Amando


    Author: amando (amando.sanz@gmail.com)
  3. Maybe due to the use of templates (others can't help with that, as you didn't post your complete reply here).

    Have you tried with shorthand definitions ?

    Kind regards,
    Richard


    Author: richard.gill (richard.gill@agfa.com)
  4. Hi With shorthand definitions OK, but with templates does not work. Is it a bug? Kind regards Amando


    Author: amando (amando.sanz@gmail.com)
  5. Hi

    I don't know if it's a bug, but if the behavior was different in previous versions of Uniface, clearly yes it is. You should try the same thing with Uniface 8 for example, and if you don't have the same result, create a test set for Compuware (opening a call on the frontline).

    Kind regards,
    Richard


    Author: richard.gill (richard.gill@agfa.com)
  6. Hi, I performed the same test in version 8. The V8 retains the length defined in the templates to make "load fields", the v9.4.01 adjust the length and makes it 50. Does not it occur to anyone else? Amando


    Author: amando (amando.sanz@gmail.com)
  7. Hi amando,

    I'm using V8 as well and have not recognised 9.4.01 shows different behaviour.

    Thaks goodness we have lots of snow here in Frankfurt/Germany
    so I have an excuse spending a lot of time with 9.4.01 experiments.

    SUccess, Uli


    Author: ulrich-merkel (ulrichmerkel@web.de)
  8. Hi amando,

    the load-field suggests a widget size (painted) which makes sense in your application.

    So it tries to include layout issues (for dates) and defaults 50*1 for a C* field.

    Success, Uli


    Author: ulrich-merkel (ulrichmerkel@web.de)