Microsoft KB Archive/135342

= BUG: The Scope on Report command does not work as expected in version 2.x =

Article ID: 135342

Article Last Modified on 2/22/2005

-

APPLIES TO


 * Microsoft Visual FoxPro 3.0 Standard Edition
 * Microsoft Visual FoxPro 3.0b Standard Edition
 * Microsoft Visual FoxPro 5.0 Standard Edition
 * Microsoft Visual FoxPro 5.0a
 * Microsoft Visual FoxPro 6.0 Professional Edition
 * Microsoft Visual FoxPro 7.0 Professional Edition
 * Microsoft Visual FoxPro 8.0 Professional Edition
 * Microsoft Visual FoxPro 9.0 Professional Edition

-



This article was previously published under Q135342



SYMPTOMS
Specifying a scope for a report to print does not print the correct records from the table.



CAUSE
The problem is that the DataEnvironment object created when the report was created performs an implicit GO TOP command as it initializes, even if the table is already open. This is necessary so that programmatic changes to Cursor object properties, such as Filter, take effect. A unexpected side- effect of this recent change is that the Scope clauses (ALL, NEXT, RECORD, and REST) on the REPORT FORM command do not affect which the records are printed.

For example, if you have a table open and the record pointer is sitting at record 5, a REPORT FORM  NEXT 1 should print record number 5 only. However, because the DataEnvironment object performs a GO TOP command, the record pointer is re-positioned as the DataEnvironment object is initiated, so record number 1 prints - not 5.



WORKAROUND
To use the REST, RECORD, and NEXT Scope clauses on the REPORT FORM command, you must prevent the implicit GO TOP command performed by the DataEnvironment object, which can be done in any one of these ways:  Remove the table from the DataEnvironment object, and open it before running the report. -or-

 Keep the table in the DataEnvironment object, but set the AutoOpenTables property to false, and open the table manually before running the report. -or-

 Keep the table in the DataEnvironment object, and save and restore the record pointer before the report actually prints. To do this:

 Set AutoOpenTables to false for the DataEnvironment object.  In the Init event, do the following: x=0              && Create a scoped variable this.opentables  && Call the OpenTables method go (x)           && Restore the Record pointer   In the OpenTables method, save the record pointer: x=RECNO </li></ol> </li></ul>

<div class="status_section">

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

<div class="moreinformation_section">

Code to Reproduce Problem
create table repotest (mychar c(1)) insert into repotest values ('1') insert into repotest values ('2') insert into repotest values ('3') insert into repotest values ('4') insert into repotest values ('5') create report repotest from repotest goto 2 REPORT FORM repotest next 1 &&Record 2 should print but record 1 prints

Additional query words: kbvfp300 kbvfp500 kbvfp600

Keywords: kbbug KB135342

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.