>>partly because the graphics side (which used OCX controls) could not be implemented as well with JavaScript/HTML and >partly because of the printing issues above.
>
>IMO it's unlikely that javascript, CSS can't match any windows control - at least any I have seen. So I wonder what type of controls you have to use that is available in the M$ world that can't be matched. Or maybe you are talking about some sort of access to the OS.

Yes - low level access to the windows graphics API (or, with WPF, wrapper libraries that simplify the process). HTML/CSS does not and, given the cross platform/ cross browser requirement, never will approach the same level of control.

Granted the majority of applications will not need this and I'd agree that a web based solution is the best approach in those cases.

>
>Printing is and will remain a major issue for the web. As long as the web is sandboxed the only thing that really works is a print server. So something will have to change to improve printing.
>
>Johnf