Since July, 1999, some of our customers have been trying to run our EXE's with UNC pathing, but with at least one space included in the directory name(s). Whether they build a desktop icon, use Windows Explorer, or the [Run] command from the task bar, Visual Foxpro responds with an error message: File 'xxxxxx.EXE' does not exist. You and I both know for the caption of the error message to say Microsoft Visual Foxpro, that the message came from VFP's runtime library. I have polled the usual sources, but felt I had a few minutes on my hands so would post this to see what response I could garner.

PS Already tried the quote marks that work for non-VFP EXE's in desktop shortcuts.

PPS I really think this is a VFP bug, loses track of itself ? ? ?