output

[Fairlight]

Without throwing an error?!  *weary sigh*

That's some awesome sanity checking...

m->

On Wed, Jun 13, 2018 at 03:54:22PM -0400, Bruce Easton via Filepro-list thus spoke:
> Yeah - I can't answer for Windows filepro, but the behavior under
> Linux might give some clues.  If I omit the path and just try to
> output the filename, it writes it to the current working directory. 
> If it doesn't have permission to write it there, it seems to have
> thrown the output away (based on my tests using the find command).
> 
> On 6/13/18 3:50 PM, Fairlight via Filepro-list wrote:
> >If the colon was missing, I would assume relative to the current working
> >directory at the time you started the filePro binary which performed the
> >action.  If you specified only a filename for the location, then I'd expect
> >it to be named (assuming you said DPDFfilename.txt) DPDFfilename.txt.  If
> >you had pathing information, I'd expect it to have tried to store relative
> >to the starting point.
> >
> >m->
> >
> >On Wed, Jun 13, 2018 at 07:25:32PM +0000, Richard Kreiss via Filepro-list thus spoke:
> >>Having an issue that maybe someone can help me with.
> >>
> >>Create a PDF output using the -P DPF:[Location] on the command line.  The output runs but no pdf file is created.
> >>
> >>I tracked down part of the issue to an error in my command line.  I had omitted the color after the drive letter and before the backslash.  Once corrected, the output file was created where specified.
> >>
> >>My question is: Where did filePro try to or create the output file?   FilePro did not show an error that it was unable to create the output file.  Therefore, I am assuming (bad word) that the output went somewhere.  But where is a mystery.
> >>
> >>I did check all possible temp directories(folders).  PFTMP is set to c:\PFTEMP which exists.
> >>
> >>I have asked Fp support this question and have not received an answer.  That make me think that there may be a bug in the PDF creation routine.  Most ither times filePro will put up an error message when it can't create the output file.
> >>
> >>
> >>Richard Kreiss
> >>GCC Consulting
> >>
> >>
> >>-------------- next part --------------
> >>A non-text attachment was scrubbed...
> >>Name: winmail.dat
> >>Type: application/ms-tnef
> >>Size: 14599 bytes
> >>Desc: not available
> >>URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20180613/acaeb25e/attachment.bin>
> >>_______________________________________________
> >>Filepro-list mailing list
> >>Filepro-list at lists.celestial.com
> >>Subscribe/Unsubscribe/Subscription Changes
> >>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>
> 
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

-- 
Audio panton, cogito singularis.