The information in this article applies to:
SYMPTOMSCreateFile() fails on Win32s if the file name is a UNC name that refers to the local machine. CAUSEThis is a limitation of Windows for Workgroups version 3.11. The same problem occurs with 16-bit Windows-based applications using OpenFile(). RESOLUTIONDo not use a UNC name to open a file on the local machine. STATUSThis behavior is by design. MORE INFORMATIONThere is a similar limitation with Windows version 3.1 and LAN Manager. If you create a network drive and try to open a file on the same network share using a UNC name, it will fail. This also happens with 16-bit Windows-based applications. Additional query words: 1.20
Keywords : kbWin32s |
Last Reviewed: January 14, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |