Let me know if it works.  I threw the idea out there, but I am not sure if
that will bypass the hooks.

Axton

On Wed, Jul 22, 2009 at 7:27 AM, [email protected] <[email protected]> wrote:

>  Thanks, everyone, for your advice!
>
>
>
> Since this is in the test system I think I’ll use Axton’s suggestion.  When
> the time comes to move this form into our live system, I’ll export the form
> definition, then edit out the offending field before importing it into the
> new system.
>
>
>
> Thanks again,
>
> Dwayne
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [email protected]] *On Behalf Of *Shafqat Ayaz
> *Sent:* Tuesday, July 21, 2009 4:18 PM
> *To:* [email protected]
>
> *Subject:* Re: Unwanted button core field
>
>
>
> **
>
> How about Axton's approach, and if the form imports back ok then go back
> delete the form and re-import it? although the problem with that would be
> the data! you would obviously need to import the data and re-import it as
> well
>
>
>
> shafqat
>
> --- On *Tue, 7/21/09, Joe DeSouza <[email protected]>* wrote:
>
>
> From: Joe DeSouza <[email protected]>
> Subject: Re: Unwanted button core field
> To: [email protected]
> Date: Tuesday, July 21, 2009, 4:31 PM
>
> **
>
> This would be an interesting approach but MAY not work if while deleting
> the unmatched field, it recognizes the field that it is attempting to delete
> as a core field..
>
>
>
> The same goes with changing field ID's using archgid.. may not work
> with fields having a core field ID.. but would be interesting to try and use
> it.
>
>
>
> Joe
>
>
>  ------------------------------
>
> *From:* Axton <[email protected]>
> *To:* [email protected]
> *Sent:* Tuesday, July 21, 2009 11:06:33 AM
> *Subject:* Re: Unwanted button core field
>
> ** Try exporting a def, removing the fld from the def, then reimporint over
> the form, deleting unmatched fields.
>
> Axton
>
> On Tue, Jul 21, 2009 at 10:03 AM, 
> [email protected]<http://mc/[email protected]><
> [email protected] <http://mc/[email protected]>> wrote:
>
> **
>
> Dear List,
>
> I have a form with a button field with a Field ID of 54.  I have no idea
> how it got there, but I can’t delete it because it is a “Core” field.  Most
> of the time it lays there and doesn’t cause any problem.  But if I try to
> copy my form to a new form (Save Form As) I get:
>
> “Field ID is in the core field range but is not recognized : (54)(ARERR
> 404)”
>
> How can I get rid of the ~...@!@# thing?
>
>
>
> Dwayne Martin
>
> James Madison University
>
>
> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers
> Are"_
>
>
> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers
> Are"_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to