>>Derek:
>>
>>Just an interesting tidbit about this problem. When I pass a path
>>parameter such as:
>>
>>"C:\Program Files\MyApp\Start.exe" "C:\Program Files\MyApp"
>>
>>it works fine. However, if I end the path with a backslash, such as:
>>
>>"C:\Program Files\MyApp\Start.exe" "C:\Program Files\MyApp\"
>>
>>it blows up. You would think anything that is surrounded by quotes
>>would be sent as is, but here is one case where it wasn't.
>
>Could it be that the backslash is a special character? What would happen if it ended with a double backslash and a quote, i.e.
>
>"C:\Program Files\MyApp\Start.exe" "C:\Program Files\MyApp\\"
>
>Just curious. This may be another case where the underlying C is imposing its way of handling strings.


Dragan,

Never thought about using a double slash. I was baffled why this slash would cause a problem, but not the other two slashes in the same parameter. It is totally a function of where the slash is in relation to the quote.(!)

Since a path is still a path without an ending slash, we just made the rule to eliminate the last one and move on with other things.

John