Resistant to change
My company have a web application which allowing user to print a data report via an ActiveX component in the past, and due to the change of requirement from uesr, I created a new .NET control hosted in this web page with the use of crystal report today, allowing them to print the report to the printer directly.
Technical speaking, the users should never notice the change and the new report is faster and the result is exactly what they want. However, they told me that they miss the old one... as they can select printer and number of copies (that's the basic printer dialog of the browser in fact) with the old ActiveX component. Therefore, I add a <DIV> with several buttons pretending the old printer dialog... Is it a normal behavior.. or.. an example of "Resistant to change"? :S
Colt Kwong