As I understand it, using the call I'm using, ( Application-Query-Delete-Entry) is more efficient for multiple deletes than Application-Delete-Entry. I haven't tested that, but it seems to make sense. It is like deleting a list of entries on your screen at once instead of one at a time. At very least, it should cut out the GLE call to refresh the entry list after each delete.
Rick On Thu, May 29, 2008 at 1:19 PM, Craig Carter < [EMAIL PROTECTED]> wrote: > ** > > True—but as Fred mentioned, you are calling the full delete for every > record. If you put the qualification in the Run If and delete them using > request id and Application-Delete-Entry, it may solve your problem. > > > > Craig Carter > > Software Engineer, RSP > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Thursday, May 29, 2008 2:07 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Application-Delete-Query-Entry gives errors > > > > ** No, that's on Application-Delete-Entry. The syntax for * > Application-Query-Delete-Entry *is *Application-Query-Delete-Entry > "<form>" <qualification_string>. > > *Rick > > On Thu, May 29, 2008 at 12:57 PM, Craig Carter < > [EMAIL PROTECTED]> wrote: > > ** > > I believe you have to use the Request ID field with this command. Since > you are not providing that, you get the entry error. > > > > Craig Carter > > Software Engineer, RSP > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Thursday, May 29, 2008 1:52 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Application-Delete-Query-Entry gives errors > > > > ** We are running an escalation nightly that runs this command: > *Application-Query-Delete-Entry > "SHR:TmpMessages" (( 'Status' = "Sent") AND ( 'Send Time' != $NULL$ ))*. > The effect is to clear a form that contains records accumulated during the > day, but which are no longer needed. > > > > Running this creates thousands of entries in the arerror.log file (roughly, > but not exactly, equivalent to the number of records in the form) that say > this: *Thu May 29 10:31:45 2008 390603 : Entry does not exist in > database (ARERR 302)*. > > There are no errors that show up in the api or sql logs, and the records DO > get deleted. Any idea why these errors appear? I'm kinda stumped as to > where else to look for a cause. > > Rick > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
