>Okay, Borislav, your code was what led me to do this correctly. I only added some double quotes; it didn't like single quotes. The reason for the double quotes was chiefly to handle the long windows file names.
>
>Thank you very much!!!
>
>Here is the code that finally worked based on your suggestion:
>
>This code was inside a SCAN. This is the final code. Notice that the Double Quotes are surrounded by single quotes.
>
>lcParam1=oApp.cImageFolder + "\" + Photos.cFileName
>lcParam2=lcPath2PICSFolder
>lcParam3=lcImageName
>lcCommand=[RUN C:\Dev\GetData\ProcImages.EXE ] + ;
> + '"' + lcParam1 + '"' + [ ] + ;
> + '"' + lcParam2 + '"' + [ ] + ;
> + '"' + lcParam3 + '"'
>&lcCommand
>
>
I am glad you made it. One suggestion. Surround the path to EXE also in quotes because you could have a path with space in it.
Also you could use ShellExecute to do this:
DECLARE INTEGER ShellExecute IN WIN32API INTEGER, STRING, STRING, STRING, STRING, INTEGER
ShellExecute(0,[open],[ProcImages.EXE],'"' + lcParam1 + '"' + [ ] + ;
'"' + lcParam2 + '"' + [ ] + ;
'"' + lcParam3 + '"',[C:\Dev\GetData\],1)
not tested.
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.