>I think your synopsis is both an over-generalization and over-simplification of the issue. Bottom line, as consultants, I think it is incumbent upon us to educate our clients as to what source code is - and how it relates to the end-product.

Fine, if they want to be educated. If they don't, they don't. What're you gonna do--tie them to the chair? :)

>I understand you can't know everything - but the issue with source code is just too basic and fundemental. It is certiainly worth the 30 seconds or so it would take explain what it is.

There are a good many people (including my mother) who would require much longer than 30 seconds to understand the concept of "source code," believe me. :)

>Here is another good analogy. I pay you to write documentation for an application. Do I not get the core .DOC files? Granted, you could just give me the printed form. However, that would not be very reasonable....would it.

Yup, it is a good analogy, because it supports my point (that in at least some cases, all the client cares about is the final output). I write help documentation. I used to bundle up all the source documents, graphics, etc., at the end of the project and send it on off to the client. Last time, I asked if he wanted it. No, he said, just gimme the .hlp. He couldn't care less about the source.

Is he wrong? Maybe. Is he the client? Definitely. Then is he right? You got it. :)