BUG: Client-Side Recordset DTC Fails if SOM Not EnabledID: Q192038
|
If a Recordset Design Time Control (DTC) is placed on an Active Server Page (ASP) without enabling the Scripting Object Model (SOM), the Recordset DTC may fail and no data will be returned. Instead, the following error is returned either to the browser, or when the source for the page is viewed in the browser (that is, "View Source").
Microsoft VBScript runtime error '800a000d'
Type mismatch: 'Recordset1'
The code generated for the client-side Recordset DTC is written in JScript
(Javascript). The source includes a call to the escape() function to ensure
that paths to databases that include backslash characters (for example,
"\\myserver\myshare\mydata.mdb") are interpreted appropriately.
If the default language for the Active Server Page is VBScript (VBScript is
the default value), and there is no reference to JScript on the page, then
the JScript engine will not be referenced when the page is interpreted.
Since the escape() function exists only in JScript, and the JScript engine
is not referenced, then the escape() function is interpreted by the
VBScript engine, resulting in the type mismatch.
To resolve this issue, a reference to the JScript engine must be placed on the Active Server Page. This can be accomplished one of three ways:
<%@ Language=Javascript %>
<SCRIPT Language=Javascript Runat=Server>
function dummy_function() {
}
</SCRIPT>
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
Additional query words:
Keywords : kbCtrl kbVisID600bug kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: May 24, 1999