|
Lidia,
Hmmm, what happens during an upgrade installation is:
- Save old FORMAT.DAT to V2X_FORMAT.DAT
- Create new FORMAT.DAT
- Write all entries for V3.0 in FORMAT.DAT
- Loop through V2X_FORMAT.DAT and update the records in FORMAT.DAT
for the values in V2X_FORMAT.DAT
The STDFORMAT field is (probably) the only field which will cause you a
problem:
V2FORMAT.FLX (used during the upgrade):
;;STDFORMAT;;
/VALID=OA$YN/HARD=OA$_FORMAT_STANDARD/LANGUAGE=OA$_LANG_YES_OR_NO
The value for OA$_LANG_YES_OR_NO will probably be 'S,N/Y,N' in Spanish.
FORMAT.FLX in V3.0:
;;STDFORMAT;;
/HARD=OA$_FORMAT_STANDARD/LANGUAGE=SM$_LANG_YN_NUM/VALID=OA$YN:SM$_YN
The value for SM$_LANG_YN_NUM is 'Y,N/1,0', which is quite different
from V2.*.
When modifying the records during the upgrade the value for STDFORMAT
V2.X (S in your example) is put into STDFORMAT V3.0. As 'S' is not part
of the internal translation string, it will be stored as an 'S', and not
as a '1' (or 'Y' in the worst case).
A way to fix this is (in V3.0):
FOR FORMAT WITH .STDFORMAT:U == OA$Y DO -
GET #KEY = .%KEY \\-
WRITE CHANGE FORMAT %KEY = #KEY, STDFORMAT = SM$_Y
If the spanish OA$N isn't 'N', then you have to do the same for all
'Ns':
FOR FORMAT WITH .STDFORMAT:U == OA$N DO -
GET #KEY = .%KEY \\-
WRITE CHANGE FORMAT %KEY = #KEY, STDFORMAT = SM$_N
And submit an SPR (if not already done)...
Ciao,
Simon
|