The advantage of this method is that you have full control over fields in the backup form, maybe you only need 20% of the fields compared with the source form, you will be able to create/delete fields in the source form without any aut change in the archiveform. We have a check that the post-is exists in the backupform before the sourcerequest is deleted. This has been running for years without any problems.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Amen, Kevin Sent: Thursday, June 07, 2007 11:36 PM To: [email protected] Subject: Re: Archive Form Invalid ** We've also moved away from the out-of-box archiving. Instead, what we're doing now is we've made a copy of the form, called it <form-name>_BACKUP, then run an escalation that does a push-fields to the Backup form, then a run process to do an Application-Delete-Entry on the original form. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ron Tavares Sent: Thursday, June 07, 2007 13:56 To: [email protected] Subject: Re: Archive Form Invalid ** I came across this many times. It means there is a field somewhere on your original form that is not on the archive form. Or the fields have the same id but are of a different type. One time I was able to resolve this by using ar utilities to create .csv files of all the fields on both forms, then comparing the two line by line till I found where they were out of sync. Sometimes the field you create on the orginal form does not copy to the archive because the 'Views' are out of sync. If you have a .def of the form before the change, you should import that. It would probably be the easiest solution. Or, try reversing the change you made. Either case, the out-of-box archiving sucks. That's why we are getting away from it. On 6/7/07, Cathy Ward < [EMAIL PROTECTED]> wrote: ** Was there a resolution to this issue? I'm also receiving ARERR 8999. I'm getting this error when creating an archive form from the original form. I can move past the error, the archive form gets created and data gets moved. After the original form is saved with archiving enabled, I am unable to make a change in time selection or in the qualification. I receive the 8999 error again along with "Unable to Save/Update form" We're on 6.3 patch 21, Oracle 9i R2 patch 8, Windows 2003 Cathy Ward University of Michigan IT Communications ----- Original Message ---- From: "Amen, Kevin" < <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, February 28, 2007 8:18:55 PM Subject: Re: Archive Form Invalid ** Tried to add two new groups to the permissions on a field. _____ From: Action Request System discussion list(ARSList) [mailto: _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
