I turned on the SQL logs and it showed the query and the selection of all the 
fields, and then COMMIT, but then it never followed through on sending the data 
over to the ARCHIVE form. (Still saying that "Archive : Field does not exist on 
current form" on the error logs).

What I did was physically update the Archive form so that the column that was 
different is now the same (still not sure why it didn't update this when I 
updated the main form).  

Now all is working and the SQL shows the Commit and the workflow that actually 
moves the data to the ARCHIVE form.....

Weird......

Lisa
-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Grooms, Frederick W
Sent: Tuesday, February 08, 2011 6:33 PM
To: [email protected]
Subject: Re: Archive Form Errors

I wouldn't think that a missing table column would do anything (since there is 
no actual data in a table column).

If you can, turn on your SQL logs and see if you can't capture an error there.

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Kemes, Lisa
Sent: Tuesday, February 08, 2011 5:28 PM
To: [email protected]
Subject: Re: Archive Form Errors

**
More info, this happened on Dev and Prod.  I also deleted a column on the Main 
form but it is still on the archive form.

AR System 7.1p7
Windows 2003

Thanks!

Lisa
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Kemes, Lisa
Sent: Tuesday, February 08, 2011 6:27 PM
To: [email protected]
Subject: Archive Form Errors

**
I'm getting this error when my main form performs an archive every night:
 
Mon Feb 07 19:15:17 2011  1 : Field does not exist on current form (ARERR 314) 
Mon Feb 07 19:15:17 2011  Archive : Field does not exist on current form (ARERR 
314) Mon Feb 07 19:15:17 2011     Archive Errors/Warnings, archiving from  
Equipment List to Equipment List Archive : entryId EL0000000221243 Mon Feb 07 
19:15:17 2011  1 : Field does not exist on current form (ARERR 314) Mon Feb 07 
19:15:17 2011  Archive : Field does not exist on current form (ARERR 314) Mon 
Feb 07 19:15:17 2011     Archive Errors/Warnings, archiving from  Equipment 
List to Equipment List Archive : entryId EL0000000223867 Mon Feb 07 19:15:17 
2011  1 : Field does not exist on current form (ARERR 314) Mon Feb 07 19:15:17 
2011  Archive : Field does not exist on current form (ARERR 314) Mon Feb 07 
19:15:17 2011     Archive Errors/Warnings, archiving from  Equipment List to 
Equipment List Archive : entryId EL0000000224100 Mon Feb 07 19:15:17 2011  1 : 
Field does not exist on current form (ARERR 314)
 
Of course it does not tell you what form does not exists...
 
I created a def file of the main form and archive form and found that a column 
from a table is missing.  I added this column (on the main form) back when 
these errors started occurring, so I'm thinking that's the problem.
 
In looking at the AR System documentation, it looks like all changes to the 
main form get changed on the archive form (unless you delete a field on the 
main form and it has data on the archive form).  So I'm wondering why this 
didn't get changed on the Archive form.
 
Is it safe to update the Archive form?
 
 
Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-602-9460 cell
[email protected]
 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to