That is interesting.
I duplicated this and with the Microsoft sub added. Worked the same.

Perhaps there's a security feature to prevent creating a huge directory tree in one fell swoop for an existing user, but one directory at a time is ok.

>Hi Trey,
>
>That's an interesting suggestion. But, if that's what's going on "under the hood", why would the following work?
>

>MD "C:\Documents and Settings\SomeUser\Application Data\test1\"
>MD "C:\Documents and Settings\SomeUser\Application Data\test1\test2\"
>MD "C:\Documents and Settings\SomeUser\Application Data\test1\test2\test3\"
>MD "C:\Documents and Settings\SomeUser\Application Data\test1\test2\test3\test4\"
>MD "C:\Documents and Settings\SomeUser\Application Data\test1\test2\test3\test4\test5\"
>

>
>Any insight you can give to this is greatly appreciated.
>
>
>>I believe this is what's happening here.
>>The Application Data folder is Hidden by default, and its Microsoft subfolder is a System folder by default, both of which VFP is blind to.
>>IOW, VFP ignores them when checking for directory existence.
>>
>>When VFP is given the command to make a directory whose parent directories don't exist, it attempts to create the whole tree. In this case, having ignored the the Application Data/Microsoft folders, it tries to create them, giving the error.
>>