I would create a pull tool to provide the default values and error messages (much less cumbersome than David's suggestion) and then a velocity macro that uses the pull tool to produce the final result.
I was starting to lean this way last night after I wrote the message and I think it has a lot of value so will probably do it. I just have to lookup how to access a pull tool from a programatic instance.
I do like the cleverness of Davids suggestion too. While the pull tool here will provide a better encapsulation of the form handling, I like adding the context to itself for special evaluative "one-off" situations.
Thanks all!
Gerry
-- Gerry Duprey ________________________________________ SchoolsOPEN, LLC 123 North Ashley, Suite 120 Ann Arbor, MI 48104 Phone (877) 483-1944 Ext. 401 Fax (734) 661-0819
Visit us Online at www.Schools-OPEN.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
