The cause of this is that in prior versions (I want to say 5.0.1 and
earlier), core fields were allowed on display only forms, but ARS was
changed at some revision to disallow this.  If you performed an upgrade
installation, then any display only forms that contain certain core
fields would generate this error when manipulated.

Ran into this in the past but can't remember what exactly I did to
correct the problem.  Some potentials:
- archgid utility
- Export a def of the form from a server running an older version of
ars, modify the def to not include the core fields and import on the
newer server. (Think this is what I did, but this predated the archgid
utility)
- Delete the field
- Delete the form and recreate it

Axton Grams

McKenzie, James J C-E LCMC HQISEC/L3 wrote:
> **
> 
> Fred:
>  
> I might be able to test this in the near future.
>  
> James McKenzie
>  
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
> Sent: Monday, July 10, 2006 1:58 PM
> To: [email protected]
> Subject: Re: ARERR 405 exporting Display Only form to .def file
> 
> 
> **
> I think you might be able to change from a core field to some other field.
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC
> HQISEC/L3
> 
> Sent: Monday, July 10, 2006 3:53 PM
> To: [email protected]
> Subject: Re: ARERR 405 exporting Display Only form to .def file
> 
> 
> **
> 
> Fred:
> 
> Will this work with a core field?
> 
> James McKenzie
>  
> [Information on ARCHGID deleted]
> 
> __20060125_______________________This posting was submitted with HTML in
> it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to