[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2547.0. "ENTRY forms in UPDATE mode not working" by MLNTSC::DALPORTO () Thu Apr 08 1993 17:24

Hello,

ALL-IN-1 v3.0 Italian.

There is at least two forms that if called in UPDATE mode, don't work:
	  CXP$LINES     and      CXP$HOSTS
When we call the above forms both using the ALL-IN-1 options ( MGT, MSY, COM,
DL or DC) or the command <FORM xxxxxx,  we get into the forms in update mode 
but whit the menu in English 

	"Do you want to Add, Change, COpy, Delete, or Inquire:

instead of the Italian menu as in the ALL-IN-1 2.4. and  for every choice we get 
the error "%OA-I-ICR, Scelta non valida. Riprovare". (In English it should
sound like  INVALID CHOICE, TRY AGAIN).

The only way to access the above mentioned forms is to specify the access mode 
like:         " <form  xxxx/mode=yyyy ".

Same problem with form PROFIL.

Any ideas? Is it a problems only for the Italian version?

Many thanks for your help.

Augusto
T.RTitleUserPersonal
Name		DateLines
2547.1Localisation Problem?IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeThu Apr 08 1993 19:1211
    The validation string on the form ENTRYMENU comes from the symbol
    called ENTRYMENU_TABLE, which is in OA.A1$MSG. What is this set to on
    your system?
    
    On a german system, you are prompted for the English words if you call
    the form directly with <FORM CXP$LINES, and they seem to work.
    
    You may want to approach Frankfurt directly for this. Also see notes
    1788.8 and 2422.6 here.
    
    Graham
2547.2take 2.4 ENTRYMENU UTRTSC::SCHOLLAERTAjax, Ajax, Ajax...Tue Apr 13 1993 07:499
    Hello,
    
    I think this problem occurs in a number of languages. The
    faster way to fix this, without updating any message file or
    screen layout, is to use the 2.4 version of form ENTRYMENU.
    
    Regards,
    
    Jan
2547.3Looking forward to your SPR....IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeTue Apr 13 1993 12:2912
    Oh, I see. In V3.0, we replaced the hardwired ;;CHANGE;; with the
    symbol ;;OA$_MO_ENT_CHANGE;; etc. This works fine for translated
    symbols (as long as the symbols are translated!) but gets confusing in
    untranslated ones, where you still need to answer in the current
    language rather than English.
    
    So what we need is some way of specifying that an alternative version
    of ENTRYMENU (with untranslated option symbols) be used. I've spoken to
    the forms Guru, and he can't think of any way of doing this at the
    moment, since the ENTRYMENU name is hardwired into the code.
    
    Graham