[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

2606.0. "oa$function calls" by ANGLIN::HARRIS (user vicious) Thu Apr 22 1993 19:53

    ALL-IN-1 3.0-1, VMS 5.5-2
    
    customer has an application written for the BA screen. this works fine
    in 2.4, but i'm having a problem adapting it to 3.0.  i know its a
    simple fix (but with my lack of functional brain cells...)
    
    this is the code that is the problem...
    ________________________________________________________________________
    ;;C;;                                                                         
                                                                                  
    .if $SPF_ADD == ""                                                            
     then .fx display Use the SEL option to select a master first\\               
    oa$fld_done else .fx                                                          
     GET OA$FUNCTION="FORM " $SPF_ADD "/MODE=ADD/ONE_ENTRY"                 
    ________________________________________________________________________
    
    $SP_ADD does get set to BADESC (this is a form)
    
    when tha last line is executed i get the error:
    
    ________________________________________________________________________                                                                              
     %OA-W-EIFW, Error in processing form BADESC -- press GOLD MESSAGE            
     -FDV-E-DSP, Get-type call is illegal for Display Only field                  
    _________________________________________________________________________
    
    here is the ND for the FORM BADESC
    
    ________________________________________________________________________
                  Form     BADESC                                             
    ;;.TYPE;;                                                                     
                                                                                  
    Entry /Key=Formname,Grpid /Mod=Update                                         
                                                                                  
    ;;.FILE;;                                                                     
                                                                                  
    Appl$Disk:[3M.A1.Rightsgen]Mappl.dat,Formname,Grpid                           
    _______________________________________________________________
    
    
    thanks - Ann
        
    
T.RTitleUserPersonal
Name
DateLines
2606.1WAGIOSG::TALLETTGimmee an Alpha colour notebook...Thu Apr 22 1993 20:095
    
    	Is Formname a display only field?
    
    Regards,
    Paul
2606.2thanks paul.ANGLIN::HARRISuser viciousThu Apr 22 1993 23:198
    no, FORMNAME is not display only.  according to FMS, it is
    Autotab, Uppercas, Response required, Supervisor Only.
    
    the supervisor only attribute won't be a problem as its only the
    ALL-IN-1 manager who access this form.
    
    	ann
    
2606.3That looks like your problemIOSG::TALLETTGimmee an Alpha colour notebook...Fri Apr 23 1993 10:0718
>    the supervisor only attribute won't be a problem as its only the
>    ALL-IN-1 manager who access this form.
    
    	I doubt it, I think that's your problem. Supervisor only has
    	nothing to do with the manager (unless your application does
    	something special). Its an FMS attribute which effectively allows
    	you to turn fields into display only fields when FMS "Supervisor mode"
    	is off (the default). It doesn't have much to do with ALL-IN-1, and
    	ALL-IN-1 doesn't turn it on and off depending on your privs.
    
    	There were changes in this area between ALL-IN-1 V2.4 and V3.0 but
    	I forget what. I seem to rememeber it was a bit broken in V2.4.
    
    	Get rid of the Supervisor only attribute and you should be in
    	business.
    
    Regards,
    Paul
2606.4that did it!ANGLIN::HARRISuser viciousMon Apr 26 1993 19:184
    thanks Paul - removed superivisor only from the form and its appears to
    be working OK.
    
    thanks! - ann