G
Guest
I produced a set of web services utilizing OWC (office web componets). Since
we've rolled out SP2. EVERY TIME a user goes to hit one of these services
they're getting the "information bar" interception on the ActiveX control...
Now I'm all for tightening up ActiveX, but If you remove my ability to turn
it on and leave it on for a particular site.... you render this simple and
fast OWC solution practically usless to me. If in doing so you force me to
solve this problem via a complete re-work I can gaurentee it won't be in a
microsoft venue for fear you may (again at your whim!) force some other
thing on me..... These OWC applications are completely behind several sets of
firewalls dmz's etc.....(i.e., an intranet) ... so the likely hood of
spoofing or someother comprimise of my activeX control is dramatically
reduced. Microsoft really needs to give me the ability to activate activex
controls by site and not every time I hit that page! IF it was up to me the
entire SP2 rollout would be backed out from our intranet!
Flame on
we've rolled out SP2. EVERY TIME a user goes to hit one of these services
they're getting the "information bar" interception on the ActiveX control...
Now I'm all for tightening up ActiveX, but If you remove my ability to turn
it on and leave it on for a particular site.... you render this simple and
fast OWC solution practically usless to me. If in doing so you force me to
solve this problem via a complete re-work I can gaurentee it won't be in a
microsoft venue for fear you may (again at your whim!) force some other
thing on me..... These OWC applications are completely behind several sets of
firewalls dmz's etc.....(i.e., an intranet) ... so the likely hood of
spoofing or someother comprimise of my activeX control is dramatically
reduced. Microsoft really needs to give me the ability to activate activex
controls by site and not every time I hit that page! IF it was up to me the
entire SP2 rollout would be backed out from our intranet!
Flame on