New feature suggestion : Allow Temporary Items in labels ofActionkeys and ACTIONBARs

[Daniel Rodríguez]

- error messages:
We use a table and an auxiliary screen to show the messages.

- screen titles, field and other labels:
We use a table. All the titles and labels are temporary fields filled in the
INITALIZE. For reports, we use QTP to create an auxiliary subfile with all
the titles and headings.
If temporary items could be used as field's labels we would save time and
lines of code, but I realize that this can be difficult to add.

Our dictionary is in Spanish and we use tables and auxiliary screens for
field's helps, description of the screen....

We don't use CC. When we develop, we write the record in Spanish. If a
record hasn't got translation is shown in Spanish. Some users have access to
screens in which they can write the translation of error messages, labels...

- function key labels
Not dealt with yet

- menu labels and menuitem labels
Not dealt with yet

- month names (from the dictionary)
We use Spanish ones. If necesary we obtain the translations from
multilanguage tables.

- decimal character (from the dictionary)
We use ',' for decimal positions, but some functions as FORMATNUMBER doesn't
work.

- numeric item formatting
We use ',' for decimal positions: PIC "^^^.^^^.^^^,^^", but we convert
numeric fields to char in order to show decimal points when we send data to
english clients or providers.

- date formatting
We always use DDMMYYYY date format. When exporting data to Excel, we use
YYYY/MM/DD.

- collating sequences (if the data is non-English)
Not dealt with yet

- upshift/downshift sequences (if the data is non-English)
This line in the dictionary solve our problem with latin characters, but we
haven't dealt with the Polish ones yet.
ASCII8 CHARACTER SET Upshift Ascii "áÁàÀâÂéÉèÈêÊíÍìÌîÎóÓòÒôÔúÚüÜùÙûÛñÑçÇ"

We also have a problem with Oracle. Our database is UTF8 and the field size
shown by the dictionary isn't real:

Oracle table definition:
  ENTIDAD_OFICINA        VARCHAR2(8 BYTE),
  COD_POSTAL_BANCO  VARCHAR2(10 BYTE),
  NOMBRE_BANCO         VARCHAR2(30 CHAR)

QSHOW:
Item                                 Type                     Size  Occ
Offset
ENTIDAD_OFICINA           VARCHAR               10            0
COD_POSTAL_BANCO     VARCHAR               12           20
NOMBRE_BANCO            VARCHAR             122           32

We have to use the size option in all the field declared in Chars instead of
bytes, Nvarchars,...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20070731/b2e883cf/attachment.htm