Automatically save a created PDF

Hi,
I am running a report which will give output as a PDF. I would like to save this automatically to Database with our user intervention. Please let me know how to achive this.
Thanks
Venkat Ch

Hello,
You can use the plugin "BLOB Destination" :
http://www.oracle.com/technology/products/reports/pluginxchange/index.html
This destination sends the report output to the database as a BLOB (Binary Large Object) datatype. This sample is tested with Oracle Reports 9i, Oracle Reports 10g (9.0.4), and Oracle Reports 10g Release 2 (10.1.2).
Regards

Similar Messages

  • Automate Save as optimized pdf

    I would like to be able to automate - as much as possible - the Save As Optimized PDF function. I have standard selections for all fields in the function. So in order of preference:
    1. Automate the entire process from one input hot-folder to an output folder - without ever opening Adobe Pro.
         I think this could be done with a folder javascript - but I need to know the object names within Adobe to set defaults. No clue how to get those object names?
    2. Set the Save As Optimized PDF fields to a default value - so that opening the file - selecting the Save As Optimized - gives the proper results - without input from the user?
    3. Any ideas I haven't thought of?

    Answered my own questions - but for the curious.
    Set up an Action Wizard - start from a folder - no steps are needed - Save to a different folder.
    Inside the save to properties box is a selection for appending to the file name and executing PDF optimizer and all settings for the pdf optimizer - which at the moment looks like it remembers.
    put some pdfs into the input folder -
    open Pro - do not open any documents
    execute the new wizard.
    It does multiple pdfs at a time with no interaction required from the user. and appears to work very well.
    Thanks

  • FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

    An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
    GOOD NEWS
    I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
    DON'T USE "SAVE AS PDF"
    But what's wrong with "save as PDF" as currently implemented?
    The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
    (1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
    (2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
    (3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
    (4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
    (5) Some or all text in the resultant PDF file cannot be searched or indexed.
    (6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
    (7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
    (8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
    (9) Some or all page content is missing (other than margin areas).
    (10) Relatively inefficient PDF is generated.
    If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
    It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
    In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
    Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
    Whether the printer supports color (Acrobat Distiller does)
    What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
    Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
    Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
    Resident fonts (Acrobat Distiller doesn't really have resident fonts)
    Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
    Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
    Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
    Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
    Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
    DON'T USE PDFWRITER
    The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
    SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
    The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
    Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
    PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
    PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
    Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
    Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    Case 3: Acrobat 3
    Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
    - Dov

    You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

  • Coding to automatically save PDF to location

    I have created an editable PDF, I have also created a button so that the person completing the form can press to submit and clears the form for the next candidate. What I also want the button to do is rather than bring up the Save as dialogue box, automatically save to a folder on the desk top. Can you help me with the coding I need to add in Livecycle to do this?

    Well,
    for a silent saveAs function, you will have to install a custom folder level script on each computer you wanna use the form.
    You also have to ensure that the target folder is already present on those computers.
    Reader won't create the folder by itself, if it doesn't exist.
    Here a few threads you should read first.
    http://forums.adobe.com/message/2266799#2266799
    http://forums.adobe.com/message/3292113#3292113
    http://forums.adobe.com/message/3393329#3393329
    http://forums.adobe.com/message/3374450#3374450

  • Need to automate Powershell using Powerpoint creating PDF

    I've got a Windows 7 (64-bit) machine and I'm trying to use the built-in Powershell to automate PowerPoint 2010 to create PDFs from PPT and PPTX files in a folder.
    I want this to run without GUI and create a single file.
    Unfortunately, all I've been able to achieve is something that brings up the GUI and saves each page as it's own jpg in a sub-folder.
    Does anyone have a short script that can do this? 
    Careful with that VAX Eugene

    Here are dozens of scripts:
    https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=Office&f%5B0%5D.Text=Office&f%5B1%5D.Type=SubCategory&f%5B1%5D.Value=Microsoft%20PowerPoint&f%5B1%5D.Text=Microsoft%20PowerPoint
    ¯\_(ツ)_/¯

  • Save as does not Create PDF Compatible File even when the creare pdf compatible files is on, Illustrator CC 2014

    save as does not Create PDF Compatible File even when the creare pdf compatible files is on, Illustrator CC 2014

    When I open is adobe acrobat I get this message.
    "This is an Adobe® Illustrator® File that was
    saved without PDF Content.
    To Place or open this  le in other
    applications, it should be re-saved from
    Adobe Illustrator with the "Create PDF
    Compatible File" option turned on. This
    option is in the Illustrator Native Format
    Options dialog box, which appears when
    saving an Adobe Illustrator  le using the
    Save As command."

  • Created PDF form in Acrobat XI Pro, but HELP fields disappear when I save FCDT file to PDF. Please help. Thanks!

    Created PDF form in Acrobat XI Pro, but HELP fields disappear when I save FCDT file to PDF. Please help. Thanks!

    I am not aware of a field type "Help" within a PDF form. I do not see it as a form field that can be added in the form edit mode.
    Forms Central forms do not support all the features of Acrobat forms.
    Are you talking about the "Tool Tips" or a hidden field that only shows when one enters a field and is hidden upon exiting the field.

  • Uncheck "Create PDF Compatible File" and "Use Compression" as my default save preference?

    We have discovered that unchecking the "Create PDF compatible file" generates much smaller .ai files when saved.  Since we do not need them to be PDF compatible we want to save them this way every time.  But right now every time we go to save a file the box comes up pre-checked!  We have to uncheck it every time!  Surely there is a preference setting somewhere that we can change so that the default is for these boxes to come up unchecked?
    I have looked under preferences and do not see it.
    Thanks
    The Print Craftsman.

    Which version of Illustrator are you using?
    Usually those settings could be changed by modifying the AIPrefs file.

  • Save as PDF or Save Book As (pdf format) Causes Frame 8 to try to quit after creating PDF

    I have Framemaker 8p273 and Acrobat distiller 8.1.3.
    When trying to creating PDFs from books using either Save as PDF OR Save Books As (PDF) file, the PDF creates FINE but the program then attempts to quit by throwing up weird dialog boxes.
    Steps to reproduce bug:
    1.Open any book
    2.Use File-->Save as PDF or File-->Save Books As and then choose type PDF
    3.PDF created fine - no errors reported in Distiller window
    4. Framemaker then throws up a small dialog box that says "cannot quit." You cannot close this box, only click OKAY.
    The only other issue that arises might be a "cannot print some graphics - will print as gray boxes"
    5. Clicking okay brings up sequence of 5 total of the same boxes (the book file has 7 files in it including the TOC).
    6. After last of 5 "cannot quit" boxes, a new Framemaker one appears, that says "Unsaved Changes in file (book name) Save before closing?" Options are Yes, No and Cancel. Yes saves file and quite Frame. No quits Frame. Cancel leaves file open.
    I have reproduced this error multiple times with different books, using both the Save as PDF and Save Book As (PDF) commands.
    File--Print Book using Acrobat printer works fine (making sure to enable the acrobat setting so bookmarks are properly generated).
    Just frustrated that the first two options cause such an annoying error. Reported as a bug.

    Jaclyn,
    I've seen this happen when an API client attempts to close a document that doesn't exist, which defaults to closing the FrameMaker session, but the session cannot close because it's in the middle of some operation. It's normally the result of sloppy code. Do you have any third-party API plugin software running? For that matter, does anyone know if the "Save as PDF" uses an API client? If so, might be a bug in that software, although it seems that there must be something unique going on here to invoke this behavior in your case.
    Russ

  • Everytime I open a pdf file in the internet it automatically saves it on my hard drive. How do I disable this?

    I want to disable the feature that automatically saves a pdf file everytime I try to open one. I was prompted whether or not I wanted to save /repeat the task - saving/downloading - for all smilar types of files and clicked yes. I can't figur out how to turn it off

    Hi willow38946771,
    Could you please let me know what version of Acrobat are you using.
    Where are you viewing this PDF file?
    Hope to hear from you.
    Regards,
    Anubha

  • Opening up PDF in browser window automatically saves it to temp file

    Hi,
    In our application, we send pdfs to a popped open browser window for the user to access.
    One of the access features is a "Save" button on the pdf that will send an xfdf post of the form data back to the server. (we have the server url embedded in a form field an Acrobat JavaScript attached to a button does the "post").
    This usually works fine.  However, we have a few customers that complain the "Save" doesn't work.
    Turns out that the "Save" doesn't work because when the pdf is first loaded, it is being saved to a temporary file on the disk (and not held in the browser memory), so the authentication cookie of the browser session is now no longer retained with the "Saved As" copy of the pdf.  Thus, the pdf "Save" fails.
    So the question is, why does sometimes, the pdf automatically "save as" to the temporary directory, and usually it doesn't have this problem?
    We've seen this both with Acrobat Reader 8 and Acrobat Reader 9 (including the latest 9.3.).
    Thoughts?
    Thanks!

    Hi Bill and Dave,
    Thanks for the thoughts.
    I'm confident that this pdf is getting opened in IE (see attached screenshot from a customer).
    As far as additional clues...  I was banging on this on my machine (Windows 7, IE 8.0.7600.16385), and I did see it occur once.
    Thanks for the thought on the browser.  I'll query the problem customers about their IE version (the site only allows using IE).
    When it occurred, (later it dawned on me...but not at the time), the "plug-in" that opened appeared to be Acrobat Standard window (because in hind-sight, I realized that the "Save As" button was available).  The way I seemed to cause it (but cannot reproduce it now) was to change the "Documents/Save Settings/Every X minutes (to value of 1 minute)", and also the Security(Enhanced) to "Enable Enhanced Security" to "true".
    note:  I have both Acrobat 9 Standard, and Acrobat 9 Reader installed on this machine.
    When I went an reset those values to the original, it was still "stuck" in the "saving to temporary disk" mode (great because it reproduced the problem, but then I seemed to have my machine stuck in this mode).
    So I rebooted, and then the IE plug-in seems to now always run Acrobat Reader...and I had the problem no more.
    I have not yet been able to get this stuck in this mode again...
    Any thoughts would be appreciated!
    Kind regards,
    Andy

  • How do I set Adobe Acrobat X to automatically save PDFs to be compatible to versions 9 or higher?

    I want to automatically save to a reduced PDF size rather than having to go through File > Save As > Reduce Size PDF.  Can I set something up in preferences?  Thanks.

    Its not the way the versions go.
    Version go from version 1.3(Acrobat 4)  to 1.7 (acrobat 8)
    and yes depending upon what version you use it can save some bandwidth (file size) 1.7 makes the smallest most compact files plus the most up to date features are supported.
    about 75% of user around the word still use 1.5 version (Acrobat 6)  seem to be most compatible with the Internet.

  • How can I automate 'Save as PDF' in Safari?

    I routinely research stuff, then save it in PDF (it seems to be a better format that html pages).
    Is there a way I can automate this, rather than the lengthy CMD+Print>PDF>Save As PDF routine?

    You can also script the user interface with an AppleScript. The following AppleScript will save the current Safari (Version 3.1.2) page to the default location (if you want to specify another location, just remove the last keystroke return statement):
    <pre style="
    font-family: Monaco, 'Courier New', Courier, monospace;
    font-size: 10px;
    margin: 0px;
    padding: 5px;
    border: 1px solid #000000;
    width: 720px; height: 340px;
    color: #000000;
    background-color: #FFDDFF;
    overflow: auto;"
    title="this text can be pasted into the Script Editor">
    -- save the current Safari page as PDF
    tell application "Safari"
    activate
    tell application "System Events"
    keystroke "p" using {command down} -- activate print menu item
    delay 0.5
    tell sheet 1
    repeat 2 times -- tab to the PDF button
    keystroke tab using {shift down}
    delay 0.25
    end repeat
    keystroke space -- press the button
    delay 0.25
    repeat 2 times -- move to the save item
    keystroke (ASCII character 31) -- down arrow
    delay 0.25
    end repeat
    keystroke return -- activate the menu item
    delay 0.25
    keystroke return -- press the save button
    end tell
    end tell
    end tell
    </pre>

  • How do i create a form in live cycle E4 that i can save as a PDF that the user cannot save over?

    How do i create a form in live cycle E4 that i can save as a PDF that the user cannot save over?

    You can't. If the file is made read-only via the file system, the user will prompted to save as a new file if they attempt to save.

  • We use a doc template to create a purchased part spec document and then save them as pdf formatted files.  These part spec documents are also appended with the datasheets for these purchased parts.  When we want to update/revise the document, is there a m

    We use a doc template to create a purchased part spec document and then save them as pdf formatted files.  These part spec documents are also appended with the datasheets for these purchased parts.  When we want to update/revise the document, is there a method, using Acrobat, to make those updates to the pdf, or must we go back to the doc template and basically generate a new document?
    Also, our resulting pdf documents aren't searchable.  How can we generate pdf documents that are searchable?  I may want to search for a part value or name within the body of these pdf documents, but currently can't do that...very inconvenient.
    Can you assist?

    Not totally sure about the search issue. A lot depends on how you created the PDF and what is in the datasheets you attached (like are they graphics?). The doc portion should be searchable as long as you used print to the Adobe PDF printer or PDF Maker. For your use, it may be that the print is adequate. However, the result should be searchable (unless maybe you had a form with filled in fields and created the PDF with PDF Maker. I think the form data may be retained in form fields and the fields are not searchable. In that case, a print might be a better procedure. (it would help to know the versions of WORD and Acrobat as well as the exact process you used to create the PDF.)
    If the appended data sheets do not change, then you might try opening the original PDF and then using Replace Pages to replace the file created from the DOC file.

Maybe you are looking for