This is another take on an issue I raised recently where I have a standard Windows application that works as expected on my local network, but behaves differently on my client's application servers. The OS involved is Windows Server 2008 R2. The issue is concerned with the presentation of the Windows Common Dialog boxes (i.e. Print Dialog, Save File As Dialog, etc.) which display their selection options as "static-text" on my own network (as I would normally expect) but display their selection options (print devices, folders, file names, etc.) as hyperlinks on my client's application servers. This behaviour results in the end user NEVER being able to select a print device or filename without the OS taking control and processing the simple act of "selection" as if the user had both "selected and clicked the PRINT or SAVE" button (which, thereby, never allows the user access to the CANCEL button on any of the standard dialog boxes). I have never seen this type of behaviour until now, and am looking for some insight into why this might be happening and what I can possibly do or (more to the point) ask my corporate client to do to make these common dialog boxes work as they always have in the past!