Have you actually tried spaces in a UNC format address? My point is not the quote marks, but that the EXE gives an error when it loads. It does not give an error when mapped to the same directory with spaces as a drive letter, nor does it give an error when in the development version running from the command window, but it does give an error when attempting to run it from desktop icon / windows explorer / command from task bar using UNC format with space(s) in the path. I think there is a bug in the runtime code.

Thanks for at least looking at my message, I am looking for how to handle this situation ( bug in VFP ? )