This article has been archived. It is offered "as is" and will no longer be updated.
In earlier versions of the Platform SDK documentation for SHFILEOPSTRUCT, there is nothing that specifically states that wildcards cannot be used for destination. In fact, version 4.00 of the shell did allow the use of wildcards in the destination string. Later versions of the shell are stricter about this and will display an error message with the following text:
The source and destination filenames are the same.
In addition, no files will be moved or copied.
SHFileOperation was never designed to accept wildcards in the destination, however, some versions of the documentation for SHFILEOPSTRUCT do not exclude the use of wildcards. Later versions of the documentation do specifically exclude the use of wildcards in the destination.