I think judging by your path that what I am running into is the Windows system
being reticent to allow a foreign app to launch processes in certain folders.
Thankfully I have a workaround. It’s telling I think that the dictionary
describes the shell command as another way to launch documents
On 11/17/2023 4:24 PM, Bob Sneidar via use-livecode wrote:
Hi all. Given:
tTextEditorPath = "C:/Program Files/Windows NT/Accessories/wordpad.exe”
tFilePath = "C:/Users/bobsneidar/Documents/Installs/The Whole
Child/Cerritos/25528/Old Copier Settings.txt”
The command:
launch tFilePath with
In case anyone cares, this works:
if the platform contains "WIN" then
put "start" && quote & tTextEditorPath & quote && quote & tFilePath &
quote into tShellCommand
get shell(tShellCommand)
else
launch tFilePath with tTextEditorPath
end if
Bob S
> On Nov 17, 2023,
Hi all. Given:
tTextEditorPath = "C:/Program Files/Windows NT/Accessories/wordpad.exe”
tFilePath = "C:/Users/bobsneidar/Documents/Installs/The Whole
Child/Cerritos/25528/Old Copier Settings.txt”
The command:
launch tFilePath with tTextEditorPath
Does NOT launch tFilePath with tTextEditorPath,
