The information in this article applies to:
SYMPTOMSWhen you are using the intrinsic Visual Basic file system controls (for example, DriveListBox, DirListBox, FileListBox), some or all of your files are not listed. This usually occurs when you are trying to access files on a network server, but can occur locally under some circumstances. CAUSE
The following statement is copied from the Visual Basic 5.0 Programmer's
Guide (page 67) and you can also find it in the File System Controls
section of the Forms, Controls, and Menus topic in Books Online:
Note: These controls are provided primarily for backward compatibility with applications created in earlier versions of Visual Basic. The common dialog control provides an easier method of working with file access. These controls are old technology. They were not designed for, nor tested with, some of the new operating and network system software. Specifically, these controls rely on the existence of 8.3 file and directory names. Any set of circumstances that result in the unavailability of 8.3 names will cause problems. For example, you can disable the creation of 8.3 file or directory names on a Windows NT Server. If this happens, the intrinsic controls will only see those directories or files that have 8.3 names. RESOLUTION
As stated in the Visual Basic 5.0 Programmer's Guide, the best resolution
is to use the CommonDialog control. Not only is it more likely to work, it
also makes your application's user interface consistent with other Windows
applications.
STATUSThis behavior is by design. REFERENCES
For additional information, please see the following article in the
Microsoft Knowledge Base:
Q196028 : PRB: FileListBox Control May Not List File Names Properly
Keywords : kbCmnDlg kbCtrl kbVBp500 kbVBp600 kbGrpVB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |