>How do most contractors place warrenties on their
>work.

Steve:

This seem to have started a thread of interest. There are a
couple more points.

Whe a company does want a fixed bid, there is a new problem:
The specs are *never* complete, and there are things in the
specs that are not fully communicated. Just as you find in
scenario testing, you will find things the client missed. This
gives you two choices - Take the money and start programming,
knowing there may be an upset when you inform the client there
is no error-trapping, or audit trail etc in their specs, or,
spend many hours going over the specs with the client.

The correct thing is to go over the specs with the client
before you make the bid. Here I *always* let them know I will
bill them hourly - and that they can use the resulting specs
for bids from others. This gets you so intimate with the client
they are more likely to accept your bid, unchallenged.

The whole idea is to see that you *and* the client get a viable
exchange. This may also mean that you should be compensated for
code you have. The client needs a bill of materials, and you
have the code? Build in a charge. Don't give it away.

Finally, every fixed bid is a potential nightmare. I would
rather program on an original XT than make a fixed bid.

Best,
Randy