Hi Mark, 

From the picture, that looks like a datawindow property..  are you saying that we'd have to put something generic in there to stop the automatic insertion of the windows user, or will there be another property that says don't output that metadata field?

Cheers
Adrian

Hi Adrian,

Thanks for reporting this problem.

In fact, we have already provided the properties (Author, Subject, Keywords, Application, etc.) settings in our internal PB 2019 R2 Beta (see the attachment).

This functionality will be included in the next GA release.

Regards,

Hi Adrian;

   Got it ....

1) Use PDF ToolKit (free edition) - my favourite PDF tool I use called from PB Apps.  ;-)

    https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit

2) Use the command ... for example

    pdftk MyDW_PDF.pdf dump_data output info.txt

3) Edit the TXT file and replace meta data values as required

    Use FileReadEX, FileWriteEx to automate the TXT file values via PowerScript

4) Run the PDF Toolkit command ...

    pdftk MyDW_PDF.pdf update_info  info.txt output MyDW_PDF.pdf

5) New PDF file signature ... (from my quick test a few minutes ago)

/Creator (PScript5.dll Version 5.2.2)
/Title (PDF Wars)
/Producer (Lucas films)
/Author (DarthVader)
/ModDate (D:20191114105002-05'00')
/CreationDate (D:20191114105002-05'00')

HTH

Regards ... Chris

Hi Chris,

It is strange that nobody has highlighted this as an issue before given we've been producing PDFs from PB for something like 25 years.  But now someone has brought it up, we have to respond as I'm pretty sure someone is going to get seriously bent out of shape over it given the nature of the 'issue'.

I'll raise a ticket to get the ball rolling, but I'm also going to look at finding a PDF library that I could integrate into the app to modify the PDF files directly.. assuming that any kind of PB fix would be quite a ways down the road.

Cheers

Adrian

Hi Adrian;

   I just looked at my latest Native PDF generation and you are correct ...

/Subject ()
/Title (DataWindow)
/Author (Chris)
/Creator (Appeon PB)
/CreationDate (D:20191114110036-05'00')
/Producer (PDFlib 9.0.7p1 \(C++/Win32\))

    There is nothing that I know of that controls what "meta data" is ir is not placed into the PDF during the generation process. I would suggest opening up a Support Ticket for this issue.

FWIW: I also noticed that GhostScript does this as well when using the Distill! PDF generation option in the DWO.

</Producer(GPL Ghostscript 9.23)
/CreationDate(D:20191114105002-05'00')
/ModDate(D:20191114105002-05'00')
/Title(DataWindow)
/Creator(PScript5.dll Version 5.2.2)
/Author(Chris)>>endobj

Thought: I wonder if we can change this by some kind of O/S "impersonation" setting?

Regards ... Chris