BUG: Recordset DTC with Stored Procedure with Parameters Dirties the Page (191726)


The information in this article applies to:

  • Microsoft Visual InterDev 6.0
This article was previously published under Q191726

SYMPTOMS

Switching between views (for example from Source View to Design View), on an Active Server Pages (ASP) page, which has already been saved and contains a recordset DTC that is bound to a stored procedure, sets the dirty flag for that page. The dirty flag incorrectly indicates that the page contents have changed and need to be saved.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open a project with a data connection.
  2. Create a new ASP page and add a recordset DTC.
  3. Bind the recordset to a stored procedure that uses parameters.
  4. Save the file.
  5. Switch views.
  6. Close the ASP page.
  7. Notice that you are asked to save changes.
Result: The dirty flag of that page is set.

Expected: The file hasn't changed; the dirty flag should not have been set.

NOTE: This is undesirable for Web projects under Source Control. If you are switching from Source to Design view, you will get a "Check Out for Editing" dialog box. If you are switching from Design to Source view, you'll get a Visual SourceSafe dialog box that states: "This file is under Source Code Control."

You will also get these messages if you check-in the file and leave it open in the editor window.
Modification Type:MinorLast Reviewed:2/14/2005
Keywords:kbBug kbCtrl kbpending KB191726
©2004 Microsoft Corporation. All rights reserved.