Darrell, I don't think this is the best way to go about this. I think Charlie's suggestion makes more sense--first define what we need
I agree. I think it's fine to setup a test case and give it a shot, but just diving in and implementing something without really knowing if it solves the problem makes little sense.

Why put a bandaid on a problem when there is an opportunity to come up with a good fix??

--
Greg J. Zartman, P.E.
Vice-President

Logging Engineering International, Inc.
1243 West 7th Avenue
Eugene, Oregon 97402
541-683-8383 541-683-8144
www.leiinc.com


--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org

Reply via email to