BUG: setParameter Does Not Work in Client Scripting Platform (191149)

The information in this article applies to:

Microsoft Visual InterDev 6.0

This article was previously published under Q191149

SYMPTOMS

When DTC Scripting Platform is set to Client (IE 4.0 DHTML), the getParameter and setParameter methods fail to function on the Recordset design-time control (DTC). This affects stored procedures and parameterized queries.

In addition, when DTC Scripting Platform is set to Client (IE 4.0 DHTML), the getParameter and setParameter methods do not appear in the IntelliSense drop-down list box.

CAUSE

The Client DTC Scripting Platform does not support the getParameter and setParameter methods.

RESOLUTION

The workaround for this issue is to set the setSQLText property so that the parameters are a part of the SQL statement.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

The setParameter and getParameter methods fail from the client scripting platform. For example:

   rsByRoyalty.setParameter(0, 50);   //This fails.

   Recordset1.setSQLText("Select * from authors where state = ?");
   Recordset1.setParameter(0, "CA"); //This fails.

The following examples demonstrate how to set the setSQLText property to obtain the functionality of a stored procedure with parameters or a parameterized query:

   Recordset1.setSQLText('"byroyalty" 50');

   Recordset1.setSQLText("Select * from authors where state = 'CA'");

Modification Type:	Minor	Last Reviewed:	3/7/2005
Keywords:	kbBug kbpending KB191149