Maybe you should try a <@sleep> in file1.taf to give file2.taf a chance to start execution?
Also are there any user, domain or application vars in either taf that might cause file2.taf to think it is done? Just a couple thoughts. Steve Fogelson -----Original Message----- From: MC Tay [mailto:sm...@media88.com] Sent: Thursday, March 19, 2009 4:00 PM To: witango-talk@witango.com Subject: Re: Witango-Talk: Non-asyn call in Witango Thanks Robert...that works. However, I have a loop of say 50 in file1.taf triggering <@URL> to file2.taf. For some reasons the <@URL> to file2.taf ran 9 times only even though file1.taf completed the loop of 50. Any idea why? Thanks! MC At 11:15 AM 3/19/2009, you wrote: >you can do @url, and tell it not to wait. > >-- > >Robert Garcia >President - BigHead Technology >VP Application Development - eventpix.com >13653 West Park Dr >Magalia, Ca 95954 >ph: 530.645.4040 x222 fax: 530.645.4040 >rgar...@bighead.net - rgar...@eventpix.com >http://bighead.net/ - http://eventpix.com/ > >On Mar 19, 2009, at 11:09 AM, MC Tay wrote: > >>Hi: >> >>We have a situation that needs file1.taf to call file2.taf without >>having to wait for the results from file2.taf. Is there a way to do >>this? >> >>Thanks! >> >>MC >> >>________________________________________________________________________ >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
