You're going to live a much easier life if you abandon cfinsert and cfupdate. Sooner or later it will catch up to you.
However, the fix to your problem is pretty simple. <cfset form.task_id=url.task_id> <cfset form.status_id=url.status_id> <cfupdate...> Less efficient than Rick's example, and ugly all around. You can cfset whatever you like into the form scope and use it in a cfupdate without a form post etc. Someone awhile back pointed out that cfupdate effectively uses cfqueryparam in its evil work, complete with examples, so I guess if thats true (it may not be for all I know) the above isn't quite as terrifying as it looks. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192833 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
