>From David Wolverton >How do others handle CALL @ As you've pointed out, there's no really good way to do this, at least not one that's easy AND portable. So what about this idea? Create a configuration record or file that has information for all of the methods you know about, then verify against that file? That way you have the control to ensure that all the methods are installed, you have a quick and simple way of checking for a valid method, and could even translate a method name into a valid subroutine with a different name if you so chose.
-Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
