The Universal Naming Convention allows non-mapped drives to contain our VFP applications. We have hit a snag at one site, where in addition to specifying the location in UNC, spaces were included in the path name: "\\server\sharedvolumnname\D E M O\demo.exe"

The double quotes are required in the shortcut by Windows since there is at least one space / blank / chr(32) in the pathing. The desk top icon and Windows Explorer both allow double clicking, but VFP gives the message: File 'demo.exe' does not exist.

Since the only way for the message to show up is for the exe file to have been accessed, the VFP message seems misleading, and of course fatal, since [OK] really cancels the program. I added a 'Wait Window' as the first line of code in the main program of the exe's project, recompiled, and put it up in the same directory -- my message did not show, but VFP complained that it still could not find 'demo.exe'. I renamed the path from 'D E M O' to 'DEMO', and Windows removed the quote marks ( not needed since no embedded blanks in the pathing ). I then ran the exe again -- saw my message and did not get the VFP error.

Is this expected behaviour? Are space / blank / chr(32) not permitted in UNC? I hope the answer to both is 'No', so that leaves me to think that VFP has an anomoly / bug.