DOS wildcard, *, not valid with .FileName? 
Author Message
 DOS wildcard, *, not valid with .FileName?

I just ported an Access97 app from an  NT4 Terminal Server to a W2K Server
running Terminal Services, and now some code that uses the .FileName="*.txt"
statement within an Application.FileSearch section causes a runtime error.
Oddly, if I replace the "*.txt" with an actual file name it works just fine.
Anyone know why the wild card would suddenly not be support in this usage?

Thanks in advance.

Stuart



Mon, 03 May 2004 02:11:15 GMT  
 DOS wildcard, *, not valid with .FileName?

http://support.microsoft.com/support/kb/articles/Q259/7/38.ASP
OFF97: Microsoft Office 97 Programs FileSearch Fails on a Microsoft Windows
2000-based Computer

Serge Gavrilov
http://accesstools.narod.ru



Quote:
> I just ported an Access97 app from an  NT4 Terminal Server to a W2K Server
> running Terminal Services, and now some code that uses the
.FileName="*.txt"
> statement within an Application.FileSearch section causes a runtime error.
> Oddly, if I replace the "*.txt" with an actual file name it works just
fine.
> Anyone know why the wild card would suddenly not be support in this usage?

> Thanks in advance.

> Stuart



Mon, 03 May 2004 04:58:23 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Jet OLEDB provider: Valid wildcard SELECT returns nothing in ASP

2. Using WildCard (*) with .FileSearch.Filename in Access97 VBA with Windows 2000

3. Filling FileOpenDialog with filenames containing wildcards

4. Filename wildcards as arguments to script

5. valid filenames for shell functions?

6. Valid Filenames?

7. Checking for valid filename

8. Detecting if a filename is a valid picture file

9. Converting an invalid filename to a valid one

10. check string as valid filename

11. API to test for valid filename?

12. Valid FileName

 

 
Powered by phpBB® Forum Software