Re: Verify IFS Path & File name string is valid

I've found a MSDN document (http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx) that says these chars are not valid in windows file names:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

In addition, a period might also be bad since it can be used to reflect current and parent directories, though we will be specifying an explicit path.

I can create a routine to check for these, but I was wondering if there was a system API.

Sam

On 1/28/2010 7:36 PM, Lennon_s_j@xxxxxxxxxxx wrote:

I want to be sure that if the called program tries to create a file with
the path and file name that it won't fail. The resultant file will be a
PDF that will be redisplayed in a browser using a .NET app. Thus I have
the feeling that there are certain characters that can't be used, for
example ?, :, <, >.

Sam

On 1/28/2010 7:17 PM, Scott Klement wrote:

Do you mean "valid" in the general sense of "it's physically possible to
create a path with this name" or do you mean "valid" in the sense of "my
boss will allow us to utilize names like this" or do you mean "valid" in
the sense of "points to a directory that already exists"?

Or what do you mean?

If you mean in the most general sense -- I don't think there's any
possible character string that's not a valid path name.