| 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 |
Hello,
Just one more quick question. I've tried searching for notes with a
title of exceptions. Didn't get anything.
I have a student who has written ND back at his site. The form
displays in th current item block with a "(exceptions)" line.
The full message is: "This form has exception routines"
What does this mean?
Mia Ruddy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1727.1 | Part of Stars article | GIDDAY::SETHI | Man from Downunder | Fri Nov 06 1992 02:59 | 43 |
G'day Mia,
Stars article "A1 V3.0 RN] Known Problems: CM / Exception Elements
Second Language" has all the details. I'll just include a part of the
article here.
Publication Date: FEBRUARY 1992
2.4 Customization Management
o Customization Management includes definitions for a
number of special elements, referred to as exception
elements. These are elements where special processing
must be invoked whenever they are customized. The
ALL-IN-1 kit only includes the definitions for the
ENGLISH application area. However, similar definitions
are required for each language version installed on a
non-English language system.
Workaround:
o On a single language (non-English) system:
Enter Customization Management and call the entry
form CM$ETYPES interactively. Select the exception
elements. There are four exception elements:
CM$MORE$SCROLL$KEYS$INDEX
MORE$SCROLL$KEYS$INDEX
SA$MORE$SCROLL$KEYS$INDEX
FC$GOLD_E
Copy the element details, changing the area details
to the name of the language (for example, BRITISH,
GERMAN, or FRENCH.)
There is more in the article about multi-language systems.
I am would like to find out why special processing is required for
these elements, just out of interest ?
Sunil
| |||||
| 1727.2 | GET $ULTRA_CUST = "BOEING" | MELKOR::RUDDY | Home is where overhead is | Fri Nov 06 1992 05:15 | 9 |
Buenas dias, Sunil:
This student is from Boeing. Boeing has numerous customizations. I
will ask my student more about the application he was working on. I'll
get my hands on the article and read more about it.
Thanks,
Mia
| |||||
| 1727.3 | In addition to the STARS article | CESARE::EIJS | All in 1 Piece | Fri Nov 06 1992 07:48 | 38 |
Hi Mia,
An (Exception) element is like a normal element, but needs different
processing than a normal (Standard) element.
E.g. take MORE$SCROLL$KEYS$INDEX FRM. This is just an FRM, and all
processing is the same as a Standard FRM. But....
When moving to live, it shouldn't be moved to one form library only,
but to more than one. That's where the special processing starts.
Especially for MORE$SCROLL$KEYS$INDEX FRM, the procedures:
CM_SM_DELETE_MORE_SCROLL_KEY.SCP
CM_SM_MOVE_LIVE_MORE_SCROLL_KEY.SCP
CM_SM_REMOVE_LIVE_MORE_SCROLL_KEY.SCP
CM_SM_MOVE_BASE_MORE_SCROLL_KEY.SCP
have been created.
Have a look at 'Manage element types' (SM CSZ MET). You'll see two
types of records:
STANDARD FRM
MORE$SCROLL$KEYS$INDEX FRM ENGLISH
The first one is standard processing, the second one is element
specific (exception) processing.
If CM detects this you'll be warned that this is going to happen.
If the situation at Boeing is more or less unexpected, check:
- which element is being edited (there are four exceptions
- did Boeing add records to CM$ETYPES?
Ciao,
Simon
| |||||