[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

1825.0. "Overlay and CTRL/W" by AIMTEC::BUTLER_T () Fri Nov 20 1992 16:25

    Hello:
    
    I am looking into a workaround for a customer.
    
    
    
    Allendale Insurance is *very* concerned about the differences in
    behavior of formsets between V2.3 and V2.4 of ALL-In-1.  Below is an
    example:
    
    They have a formset which contains 3 forms.  All of the forms are arg
    forms.  The first form in the set has a clear area defined as 0 to
    23, taking up the entire screen.  The second form is an overlay form
    which clears 10 to 23, the bottom of the screen.  The third form
    clears 0 to 23, the entire screen.  On the first form, there is a
    .form_set which calls the other two forms.  Not all of the named data
    is on the first form.
    
    V2.3
    
    Call up the first form in the set.  Hit next screen. The second forms
    overlays the bottom of the first form.  Hit next screen.  The third
    form paints over the entire screen.  Hit previous screen.  The second
    form comes back overlaying the first form in the set.  This behavior
    occurs in V2.3 of ALL-IN-1.  Also, if while the second form is on the
    screen, you hit Ctrl/W the top half of the screen is not cleared.
    
    In V2.4, the behavior is entirely different.  Call up the first
    form.  Hit next screen.  The second form overlays the bottom of the
    screen and on the top halp of the screen is part of the menu from
    which the formset was called.  Hit next screen and the third form
    paints fine.  Hit previous screen and the second form reappears
    overlaying the menu again.  On their system if in V2.4 you hit Ctrl/W
    while the second form is on the screen, it clears the top half of the
    screen leaving it blank.  I cannot reproduce this clearing of the top
    half of the screen.
    
    Note: V3.0 works as described for V2.3.  The customer can not upgrade
    to V3.0 due to customization investments.
    
    I think they would be *very* happy with a workaround to their
    problem.  But they would possibly settle for the resons why this
    change occurs and some suggestions they might try to fix the problem.
    
    Any Help is Appreciated,
    
    Tim

T.R	Title	User	Personal Name	Date	Lines
1825.1	Overlay and CTRL/W	AIMTEC::BUTLER_T		`Mon Nov 23 1992 14:56`	13
	I realize Allendale has not learned how to spell ALL-IN-1 (I thought that would get a comment) and I realize that there is not much we can do about this. This is a situation, and any feedback we could use would be gratefull. Otherwise, the customer will go the sales exec route and cld. Thanks, Tim
1825.2	Will the CLD do any good?	SIOG::T_REDMOND	Thoughts of an Idle Mind	`Mon Nov 23 1992 15:22`	15
	Tim, I haven't commented so far, but it's mostly because I don't have a set of forms that do what Allendale have been up to and I don't have the time to build one. Form processing does change from time, normally to correct reported bugs, and it is quite likely that a fix has closed off one of the undocumented loopholes that facilitated the behaviour Allendale wants to recapture. I'm sure some would comment further if a set of forms, in a library, was made available on the network (not posted in this conference). Can Allendale provide a copy of such a library, complete with all of the named data they use? Tony
1825.3	Will set-up pointers	AIMTEC::BUTLER_T		`Mon Nov 23 1992 18:46`	12
	Thank You. Laurie will post a pointer to the forms, in another reply. -< Will the CLD do any good? >- No. That is why I am trying to avoid all the calls and paperwork and ... Thanks, Tim
1825.4	One big .flg file.	AIMTEC::SIMPSON_L		`Mon Nov 23 1992 19:19`	233
	Below is a listing of the three arg forms I set up. Thanks. Laurie ! FMS Form Description Application Aid ! Version V2.4 FORM NAME='TESTARG1' AREA_TO_CLEAR=1:23 WIDTH=80 BACKGROUND=CURRENT ; TEXT (1,1) 'AAAAAAAAAA' ; TEXT (2,1) 'AAAAAAAAAA' ; TEXT (3,1) 'AAAAAAAAAA' ; TEXT (4,1) 'AAAAAAAAAA' ; TEXT (5,1) 'AAAAAAAAAA' ; TEXT (6,1) 'AAAAAAAAAA' ; TEXT (7,1) 'AAAAAAAAAA' ; TEXT (8,1) 'AAAAAAAAAA' ; TEXT (9,1) 'AAAAAAAAAA' ; TEXT (10,1) 'AAAAAAAAAA' ; TEXT (11,1) 'TESTARG1' ; TEXT (11,33) ' Arg Form Title ' BOLD ; TEXT (15,2) 'Field 1:' ; TEXT (17,2) 'Field 2:' ; TEXT (19,2) 'Field 3:' ; TEXT (22,2) 'Enter information and press RETURN' ; ATTRIBUTE_DEFAULTS FIELD CLEAR_CHARACTER=' ' NOAUTOTAB BLANK_FILL NOBLINKING NOBOLD NOREVERSE NOUNDERLINE NODISPLAY_ONLY ECHO NOFIXED_DECIMAL LEFT_JUSTIFIED NOSUPERVISOR_ONLY NOSUPPRESS NOUPPERCASE ; FIELD NAME='FIELD_1' (15,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_2' (17,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_3' (19,11) PICTURE=30'X' UNDERLINE ; ORDER BEGIN_WITH = 1 NAME='FIELD_1' NAME='FIELD_2' NAME='FIELD_3' ; NAMED_DATA INDEX=1 NAME='.TYPE' DATA='ARG/OVERLAY/HARD="YOUR arg form name"' ; NAMED_DATA INDEX=2 NAME='.FORM_SET' DATA='TESTARG2,TESTARG3' ; NAMED_DATA INDEX=3 NAME='FIELD_1' DATA='/HARD="Description of field 1"' ; NAMED_DATA INDEX=4 NAME='FIELD_2' DATA='/HARD="Description of field 2"' ; NAMED_DATA INDEX=5 NAME='FIELD_3' DATA='/HARD="Description of field 3"' ; END_OF_FORM NAME='TESTARG1' ; ! FMS Form Description Application Aid ! Version V2.4 FORM NAME='TESTARG2' AREA_TO_CLEAR=10:23 WIDTH=80 BACKGROUND=CURRENT ; TEXT (11,1) 'TESTARG2' ; TEXT (11,33) ' Arg Form Title ' BOLD ; TEXT (15,2) 'Field 4:' ; TEXT (17,2) 'Field 5:' ; TEXT (19,2) 'Field 6:' ; TEXT (22,2) 'Enter information and press RETURN' ; ATTRIBUTE_DEFAULTS FIELD CLEAR_CHARACTER=' ' NOAUTOTAB BLANK_FILL NOBLINKING NOBOLD NOREVERSE NOUNDERLINE NODISPLAY_ONLY ECHO NOFIXED_DECIMAL LEFT_JUSTIFIED NOSUPERVISOR_ONLY NOSUPPRESS NOUPPERCASE ; FIELD NAME='FIELD_4' (15,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_5' (17,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_6' (19,11) PICTURE=30'X' UNDERLINE ; ORDER BEGIN_WITH = 1 NAME='FIELD_4' NAME='FIELD_5' NAME='FIELD_6' ; NAMED_DATA INDEX=1 NAME='.TYPE' DATA='ARG/OVERLAY/HARE=''YOUR arg form name"' ; NAMED_DATA INDEX=2 NAME='FIELD_4' DATA='/HARD="Description of field 1"' ; NAMED_DATA INDEX=3 NAME='FIELD_5' DATA='/HARD="Description of field 2"' ; NAMED_DATA INDEX=4 NAME='FIELD_6' DATA='/HARD="Description of field 3"' ; END_OF_FORM NAME='TESTARG2' ; ! FMS Form Description Application Aid ! Version V2.4 FORM NAME='TESTARG3' AREA_TO_CLEAR=1:23 WIDTH=80 BACKGROUND=CURRENT ; TEXT (1,1) 'BBBBBBBBBB' ; TEXT (2,1) 'BBBBBBBBBB' ; TEXT (3,1) 'BBBBBBBBBB' ; TEXT (4,1) 'BBBBBBBBBB' ; TEXT (5,1) 'BBBBBBBBBBBB' ; TEXT (6,1) 'BBBBBBBBBBB' ; TEXT (7,1) 'BBBBBBBBBBBB' ; TEXT (8,1) 'BBBBBBBBBBBB' ; TEXT (9,1) 'BBBBBBBBBBBBB' ; TEXT (10,1) 'BBBBBBBBBBBB' ; TEXT (11,1) 'TESTARG3' ; TEXT (11,33) ' Arg Form Title ' BOLD ; TEXT (15,2) 'Field 7:' ; TEXT (17,2) 'Field 8:' ; TEXT (19,2) 'Field 9:' ; TEXT (22,2) 'Enter information and press RETURN' ; ATTRIBUTE_DEFAULTS FIELD CLEAR_CHARACTER=' ' NOAUTOTAB BLANK_FILL NOBLINKING NOBOLD NOREVERSE NOUNDERLINE NODISPLAY_ONLY ECHO NOFIXED_DECIMAL LEFT_JUSTIFIED NOSUPERVISOR_ONLY NOSUPPRESS NOUPPERCASE ; FIELD NAME='FIELD_7' (15,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_8' (17,11) PICTURE=30'X' UNDERLINE ; FIELD NAME='FIELD_9' (19,11) PICTURE=30'X' UNDERLINE ; ORDER BEGIN_WITH = 1 NAME='FIELD_7' NAME='FIELD_8' NAME='FIELD_9' ; NAMED_DATA INDEX=1 NAME='.TYPE' DATA='ARG/OVERLAY/HARD="YOUR arg form name"' ; NAMED_DATA INDEX=2 NAME='FIELD_7' DATA='/HARD="Description of field 1"' ; NAMED_DATA INDEX=3 NAME='FIELD_8' DATA='/HARD="Description of field 2"' ; NAMED_DATA INDEX=4 NAME='FIELD_9' DATA='/HARD="Description of field 3"' ; END_OF_FORM NAME='TESTARG3' ;
1825.5		SIOG::T_REDMOND	Thoughts of an Idle Mind	`Fri Nov 27 1992 14:20`	8
	Tim, I've had a look and can't see any quick way around this problem. It's curious that things should have changed between V2.3 -> V2.4 and then back again at V3.0. What customization problems are preventing Allendale from moving to V3.0? Cheers, Tony
1825.6	Allendales' CM	AIMTEC::BUTLER_T		`Tue Dec 01 1992 15:33`	16
	Tony, Allendale "reee-designed" CM completely! They went way beyond anything CMA would do. They have many different solutions they market in the Insurance Industry. I worked some INSTALL/EXECUTE Issues with them and found that only one person in their programming organization understood their "CM." It is their own problem as V3.0 CM+ could work for them. I am just trying to save lots of calls, cld's, etc.. Thanks, Tim
1825.7	What did they change?	IOSG::SCM	CM+ Development Team from Torino	`Wed Dec 02 1992 08:07`	9
	Hi Tim, Just out of curiousity, what kind of functionality did they add? Something which isn't available in V3.0 either? Ciao, Simon
1825.8	Their way -vs- our way	AIMTEC::BUTLER_T		`Wed Dec 02 1992 13:19`	20
	Simon, They went to their own elaborate scheme using vms logicals as they saw it. The logicals were used to create a product (by customer) specific save set (libraries, TXL's, etc..) that would install in the site area on the target machine. Iain and I spent many a day working with VMS and logicals helping them to make it work? In fact the actual working system was more complicated ((:^)) than CM+. It was more a matter of MY WAY than CM's way. I also suspect that it is easier for them to do it their way (2.3) than to spend the resources to convert. Tim (Now I will call them and give them another reason to go to V3.0)