> From: Adam Churvis > > For example, John's modification where a login name is used > in place of the email address could be codified into a > KnowledgeBase article as a "supported hack" that, if we know > it's in the problematic app, we can handle without a problem. > > We could have many such "supported hacks" that would be no problem.
I might be in a minority here, but I think this should be an option in the framework rather than a Hack, being able to specify Login Name rather than Email Address is fairly fundamental Just my $0.02 on that ($0.03 Canadian and about 1p English) On the support issue, if anybody makes any changes to the framework you shouldn't be held responsible for it, it's almost like they're "voiding the warranty", so they have to pay for your time to fix the mess they've made <g> Cheers, Phil ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
