| 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 |
ALL-IN-1 v.3
In the Getting Started guide for Application programming, it
refers you to ABE to access MORE$SCROLL$KEYS$INDEX on page
4-17 because you are getting the anticipated error:
-OA-E-FLCMOREFRM, .MORE form MORE$SCROLL$KEYS$INDEX not found
%OA-E-FLCCOMERR, Error encountered compiling form CAR_INDEX
However if I select MORE$SCROLL$KEYS$INDEX and try and either
do a read or copy it, I get "Operation not supported for this
element"
I remember from my v.3 training that this form is marked an
Exception because you can't delete it from the development
area, but why can't I copy it or read it?
Or am I just a poor misguided fool?
Thanks
julia CSC
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 855.1 | User error? | AIMTEC::WICKS_A | DEC Mail Works for ME sometimes | Thu Jun 11 1992 21:19 | 22 |
Julia,
You are a poor misguided ..... (:==:)
It works for me - I can read it fine using those context-sensitive
thingies and when I try and copy it I get the message
Exception routines will be used, do you want to continue? [Y/N]
which reults of it coming out of OAFORM and into DEVELOP and all that
sort of stuff.
Are you by any chance on a system that went through many SSB and even
non-SSb baselevels and some of the baselevel post-install tasks weren't
done?
Put on trace and see where it's failing or take two aspirin and call
you local CSC in the morning (:==:)
Regards,
Andrew.D.Wicks
| |||||
| 855.2 | Check CM$ETYPES | FAILTE::LAAHS | An accumulation of Celts | Fri Jun 12 1992 13:14 | 12 |
Julia,
It sounds to me as if the record in CM$ETYPES for
MORE$SCROLL$KEYS$INDEX FRM is incorrect.
Use the CM$SM MET option and look at the various READ and PRINT records.
They should look exactly the same as that for the STANDARD FRM
records.
Can you read a non-exception FRM?
Kevin
| |||||
| 855.3 | Only a problem in the non-English kit | KERNEL::SMITHERSJ | Living on the culinary edge.... | Mon Jun 15 1992 11:24 | 29 |
Thanks to everyone for their replies. It looks like this is
detailed in the Release Notes.
...
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.)
| |||||