PRB: Status Bar Does Not Reset in SysCmd() Function Example

Article ID: Q120148
Creation Date: 04-SEP-1994
Revision Date: 19-SEP-1996

The information in this article applies to:

Microsoft Access version 2.0, 7.0

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

The example of the SysCmd Function topic in the Microsoft Access help index (Example 1 in the Microsoft Access 2.0 online help), is missing some lines. The missing lines are in the following section of the example:

In Microsoft Access for Windows 95 version 7.0:

    rst.Movenext          ' Go to next record.
         Next lngX
    GoSub CloseObjects

In Microsft Access 2.0

    MySnapshot.MoveNext   ' Go to next record.
    Next X
    GoSub CloseObjects

If you re-create the example with the missing lines, the progress meter will not reset after the function finishes. Instead, the progress meter will remain at 100%.

RESOLUTION

Add the missing lines when you re-create the example, so that the section reads as follows:

In Microsoft Access for Windows 95:

    rst.Movenext          ' Go to next record.
         Next lngX
    ' xx is a dummy variable so SysCmd(SYSCMD_CLEARSTATUS) can be set.
    dim xx as variant
    xx = SysCmd(SYSCMD_CLEARSTATUS)
    GoSub CloseObjects

In Microsoft Access 2.0:

      MySnapshot.MoveNext   ' Go to next record.
   Next X
   ' xx is a dummy variable so SysCmd(SYSCMD_CLEARSTATUS) can be set.
   dim xx as variant
   xx = SysCmd(SYSCMD_CLEARSTATUS)
   GoSub CloseObjects

REFERENCES

For more information about SysCmd() function, search for "SysCmd" and then "SysCmd Function" using the Microsoft Access for Windows 95 Help Index.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.