James Courtier-Dutton wrote: > Ah! but Project A and Project B might be using the same one, they > just don't know! ;-) Doesn't matter -- the dealbreaker is not differences or similarities between the two projects, but in the differing environments, circumstances surrounding the two. Not the content, but the /context/. A joke good to us ("Never trust a program if you don't know its source") will get you marked down for spouting truisms among the noncognoscenti. The context kills it -- not the content. A & B may be ostensibly identical, but the training regime may be different, so might issue-tracking in the live system. And after those have been 'fixed' we've lost what little internal insight we had intp whether training was best done one way, or another. We might also drive issue-tracking vendor B to the wall and discover that vendor A, now a monopoly provider, has us over a barrel. > Me thinks I will sound like I am quoting "Yes > Minister" soon. Quote ." I couldn't ... *possibly* ... comment! Cheers, -- Alistair Mann -- Gllug mailing list - Gllug at gllug.org.uk