>Unfortunately, these web forms are user entry interfaces for dynamic reports. Every control is absolutely necessary for the report to have the parameters needed for the VFP report to run. Since the user base for the web version is Upper management with the emphasis on "upper", they are expecting to see the same screen when they use the reports in their browser. This means the interaction between client side and server side on this particular app is, putting it mildly, complex. Anyway, it does appear to be the way IE handles layering that is at issue here. I wonder though, since IE is MS and .net is MS, why wasn't this addressed?
>
>You don't need to answer that
...
I won't. You won't want me to get started on Microsoft's lack of browser innovation since they took over the browser landscape.
I'm just giving you a little forewarning <g>... Complex Web forms are a PITA to use - not just to build! It's often better to split up real complex forms into multiple step forms or Wizard like interfaces that group things logically together.
+++ Rick ---
>>Trying to make web forms run like WinForms is an effort in futility to say the least. Yeah it can be done but it WILL cost you tons of money and time. Add cross browser functionality and you can easily double that effort.
>>
>>The principle is Keep it Simple <g>...
>>
>>Ah, ranting on...
