>Jess ---
>
>As far as I am concerned, I do not allow clients to dictate to me the tools to use on a project unless there is a very compelling reason to do so (such as additions or modifications to an existing application). If a client insists on a development tool and my analysis indicates to me that he/she would best be served by another tool, I lay down the law. I just won't take on the project if I feel that the client is pushing the wrong approach....

I agree. But if the development tool has a good reputation and support substantiated by what they hear and read, then these case of arguments bet. developers and clients will be much avoided.

>
>
>>>Many of us work as consultants. That does not mean you do what the client wants, but you consult with them. It's just like talking to a lawyer, accountant, or doctor...the advice should be given as to what is the best thing to do for the client's business. The "I advise you to do this because...." should be a major part of the consultant's discussions.
>>
>>Not all the time Craig. There are clients who are well aware of what's happening in IT world specifically on software development. And these clients wanted their investments to be safe in a long term basis, that's why we can not dictate what we want. A client or a patient relies on the ability and expertise of the Lawyer/Doctor/Accountant but not IT clients. No matter how good or expert an IT consultant is, or a Developer, the client have to think even hundred times if the development tool he is using has no good profile, no much support etc. It takes two to Tanggo: The Developer and The Development Tool.