G
George Hester
Sometimes Microsoft says the following should be in all DAP pages or "it
won't work."
<SCRIPT language=vbscript event=Current(oEventInfo) for=MSODSC>
<!--
-->
</SCRIPT>
and other times they say the following must be in all DAP pages or "it won't
work."
<SCRIPT language=vbscript event=Current(x) for=MSODSC>
<!--
-->
</SCRIPT>
I have been a little confused about this. What exactly are we trying to
catch with this event on the MSODSC control? Since it is more likely to get
a Google return on oEventInfo than a return on x, I found a page that
describes oEventInfo in practice. Here:
http://support.microsoft.com/kb/307253
And yes nontrivial results occur with the example they show on this page.
But I would like any further information on this event usage that may be out
there. Thanks.
won't work."
<SCRIPT language=vbscript event=Current(oEventInfo) for=MSODSC>
<!--
-->
</SCRIPT>
and other times they say the following must be in all DAP pages or "it won't
work."
<SCRIPT language=vbscript event=Current(x) for=MSODSC>
<!--
-->
</SCRIPT>
I have been a little confused about this. What exactly are we trying to
catch with this event on the MSODSC control? Since it is more likely to get
a Google return on oEventInfo than a return on x, I found a page that
describes oEventInfo in practice. Here:
http://support.microsoft.com/kb/307253
And yes nontrivial results occur with the example they show on this page.
But I would like any further information on this event usage that may be out
there. Thanks.