Knowledge Base

BUG: Init Method for Cursor Object has Incorrect Data Session

Article ID: 134213

Article Last Modified on 5/7/2003

APPLIES TO

This article was previously published under Q134213

SYMPTOMS

When running a report with a private data session, the Init method of a cursor or relation object with the data environment does not run with the correct data session selected, but instead runs with the default data session (1).

RESOLUTION

There is no way to know which data session should be selected with the SET DATA SESSION command because reports do not have a data session number property as forms do. As a result, any code in the Init method of a cursor or relation object is unable to reliably access the work areas of the proper data session, so the code must be placed in a different object method. A suggested alternative is to move the code from the Init Method of the cursor or relation object to the Init Method of the Data Environment object.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Create a new report.
  2. On the Report menu, click Private Data Session.
  3. Open the data environment for the report.
  4. Add a table to the data environment.
  5. Select the properties for the CURSOR1 object in the data environment.
  6. Add a SUSPEND command to the Init method for the CURSOR1 object.
  7. Preview the report.
After the SUSPEND command executes, open the View window and you will see that the default data session is selected, not the private data session.

Additional query words: kbvfp300 kbvfp500 kbvfp600

Keywords: kbbug kbenv KB134213


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.