DOCERR: SHFILEOPSTRUCT pFrom and pTo Fields Incorrect

Last reviewed: January 26, 1996
Article ID: Q133326

The information in this article applies to:

Microsoft Win32 Application Programming Interface (API) included with:

    - Microsoft Windows NT version 3.51
    - Microsoft Windows 95 version 4.0

SUMMARY

The documentation for the SHFILEOPSTRUCT structure in the Win32 SDK describes the pFrom and pTo fields incorrectly as:

    pFrom
        Pointer to a string that contains the names of the source files.
    pTo
        Pointer to a string that specifies the destination for the moved,
        copied, or renamed file.

This is only partially correct. The pFrom and pTo fields are actually pointers to a list of strings containing the desired source files. The strings should be separated by NULL characters with an extra NULL terminator after the last file name. For example, if pFrom should contain FILE1.ABC, FILE2.ABC, and FILE3.ABC, the memory pointed to by pFrom should be:

    "FILE1.ABC\0FILE2.ABC\0FILE3.ABC\0\0"

If only one file is being passed in pFrom, it should still be double-NULL terminated.

Additional reference words: Win95 Shell SHFileOperation Windows 95 4.00
KBCategory: kbui kbdocerr
KBSubcategory: UsrShell

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.

Last reviewed: January 26, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.