>    They send it out faulty as they cannot find all bugs as they cannot
create
>    all possible working conditions, if they did it would be out of date b4
it
>    was released (I don't agree with this mind!)
>
>If you disagree, you're welcome to release a competing product with zero
>bugs.  If you're right, it should sell like gangbusters, even without a
>competitive set of features, right?  Actually, I keep telling people that
>some features are bugs if they're missing.  If a customer would rather have
>nested macros (a feature) with a bug preventing a macro from terminating in
>the middle of a line (allowing foo: db mymacro(a,b,c), x, y), then who's to
>say which is a bug and which is a feature?
>
>(of course, what we find in real life is that customers want "the stable
>version" with "just the new features *I* want", apparently not associating
>the addition of features with the addition of bugs...  Bah...)
>
>If you think you know how to test software, I suspect we have a job opening
>you could fill...
>
>BillW

Bet you don't agree with having to die one day but thats just the way it is
I was just stating the facts!! keep your hair on!! and when i finish uni
i'll hold you to the job offer!! ta!
Also keeping this subject going will only damage your sales so why not give
the guy a new copy (i'll send you some blank disks if your too tight) and
keep the peace? and if you were in customer relations in any company of mine
you'd be sacked!! for the price of a couple of disks you could have had
someone come on here praising you and who knows how many new customers that
would have brought, tight as a gnats chuff eh??.
yours' all wound up,
                               Andy.

Is this [OT] now???