System Command

[Brian K. White]

On 4/17/2013 11:15 AM, Kenneth Brody wrote:
> On 4/17/2013 11:01 AM, Richard Tartaglia wrote:
>> I am running FilePro 5.0.14 using windows XP.
>>
>> I have an @key process to save a PDF file or display that PDF saved in a
>> blob field. Everything worked great until I updated Adobe to a newer
>> version. Of course the system prompt can’t find Adobe until I update my
>> code in FilePro to the new version of Adobe.
>>
>> Is there a way to get the version from windows, put it in a variable for
>> FilePro and then use it for the prompt to display the PDF.
>
>   From your description, I am going to assume that you start Adobe Reader by
> passing the full path to the executable, such as:
>
>       "C:\Program Files (x86)\Adobe\Reader 10.0\Reader\AcroRd32.exe"
>
> There's no need to do that.  If you have a PDF file with a ".pdf" extension,
> all you need to do is execute
>
>       start \full\path\to\filename.pdf
>
> and Windows will execute the default PDF reader, regardless of what program
> that is or where it's located.
>
> Note, however, that there is a "feature" is the start command that you need
> to know about if the filename needs to be in quotes.  (For example, if the
> file is "c:\Documents and settings\Richard\temp\foo.pdf".)  If you were to
> execute a command such as:
>
>       start "c:\path to\filename.pdf"
>
> you will get a command prompt with "c:\path to\filename.pdf" as the window
> title.  To prevent this from happening, put a pair of quotes prior to the
> filename:
>
>       start "" "c:\path to\filename.pdf"
>

Forgot about that one.
God I hate Windows.
There is some even worse real bizzarro insanity with quoting arguments 
to cmd.exe.

-- 
bkw