>George,
>
>I think this is a classical example of my stupidity :) Very simple - and works great!
>

Not stupidity; at worst, ignorance. Ignorance is correctable - stupidity seems to be an eternal condition.

Now for the Why - many things need to be told not to use characters embedded in LFNs as separators or terminators in their internal processing; the convention used is to encapulate the string in double quotes (") to tell the parser to treat the entire string as a path. You can see this in use if you look at paths in shortcuts that have an embedded space.

This is not universal, and some parsers aren't very swift - they get confused if you quote-encapsulate something that doesn't need quote encapsulation.

You can see this at work if you macro-expand paths for VFP command lines - the use of name resolution rather than macro expansion is a frequent workaround.

>>
>>This works! Thanks a lot. Now I'll do these changes in Archive program.
>>
>>>>If I pass 'c:\test\*.*', 'c:\test\ggg.zip', it works.
>>>>If I pass 'c:\My Documents\*.*', 'c:\My Documents\ggg.zip', it failes.
>>>>
>>>
>>>You may need to further quote encapsulate LFNs that contain a space - try using
>>>'"c:\My Documents\*.*"', '"c:\My Documents\ggg.zip"'