Since a CF Scheduled task is basically just a call to a webpage, just put a <CFLOCATION> in your code.
So, your scheduled task will be calling task1.cfm, and the last part of your code would be a <CFLOCATION URL=" task2.cfm" /> If you are only doing queries, the best way to do it would be on the SQL side. A stored procedure as a SQL job would be the way to go. That way, you can wrap everything around a transaction and rollback when it breaks. It'll be faster, plus if you use a CF Scheduled Task, you will be breaking out your queries and you cannot do CFTRANSACTIONs. And, yes, even though you can still do regular transactions, bear in mind that if your CF errors out with open transactions you will run into locking issues. Doing this on the database side is the best way to approach this. Rick Faircloth wrote: > Thanks, Mike and Mary Jo... > > Questions: > > I'm not able to think of how to code a task to "call" > another... nothing's coming to mind. How would I accomplish that? > > Also, the logic to insure a previous task completed... such as > a variable that is set to "true" or something like that? > > And, Mary Jo, concerning rollback...would cftransaction be appropriate? > The processes aren't dependent upon one another, they are just long-running > and rather processor intensive so I don't want any concurrent tasks running. > > If I were to put all tasks into one long file and put them into a single > named thread, would that be a good approach? Problems with that? > > Thanks for the suggestions! > > Rick > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:306022 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
