Call Pop-up Dialog created in SE51 from report

Hi All
I've created a screen YTESTPOP screen number# 5005 of type 'Modal dialog box' and assigned the elements. Now i want to call this screen as a pop-up from a report say ydisplay_arrears. Though i had followed all the seting when i call the screen using call dialog it is not taking the shape of a pop-up window rather it is coming up as a full screen. not sure what i'm missing with. any inputs on this?
pls do not give sugestion as use popup function module (i'm aware of it) and it is not desired for my requirement.
thkx

Try this way
call screen 5005 starting at 7 8
ending at 77 13.
a®

Similar Messages

Problem in creating text file from report file

Hello Everybody...
I have problem in creating text file.
I had set System Parameter as below
DESTYPE : File
MODE : Character
DESNAME : gayu.txt
And ruler setting
Units : Character Cells
Character Cell Size : Horiziontal = 7
Vertiacle =12
GridSpacing : 1
no of snap points per grid spacing : 1
but when i run report it will give error
"REP_1219 M_2 or R_2 has no size -- length or width zero"
so is there any solution of that
or another way to convert report into text file?....

Hi Folks,
Please don't go after that Error as its a very deceptive one. Please don't go for altering your design Or changing the size of items in your layout.
Similar errors I have come across in reports. I think its due to file transfer type. You might have transferred the file in Binary and your File Mode I am seeing it as CHAR.
This normally happens while making the Report Format as "Text". Either you change that format which I think is possible in your case as your basic requirement is making a report output of CHAR type.
Please check for this error in Metalink and proceed accordingly. I could fix similar errors when I changed Format type to PDF(from text).
Regards
Shibu

Creating PDF (FOP) from report in Apex 3.0 generates Error 500 (solved!)

Hi, I have installed apex 3.0 , no errors, followed the installationguide for standard support printerserver (FOP) and OC4J (standalone downloaded) is up and running. 
 
However, when I click print, I get a 1 byte PDF with the text: 
<HTML><HEAD><TITLE>500 Internal Server Error</TITLE></HEAD><BODY><H1>500 Internal Server Error</H1><PRE>Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.</PRE></BODY></HTML>
 
 
 
And when I check global_applications log I find: 
 
 
07/03/26 14:44:33.205 defaultWebApp: Servlet error
oracle.xml.xpath.XPathException: Parse Error in number function.
 at oracle.xml.xslt.XSLBuilder.startElement(XSLBuilder.java:468)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1288)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:319)
 at oracle.xml.xslt.XSLProcessor.newXSLStylesheet(XSLProcessor.java:708)
 at oracle.xml.xslt.XSLStylesheet.<init>(XSLStylesheet.java:321)
 at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:114)
 at apex_fop__render._jspService(_apex__fop__render.java:71)
 at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.2.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:597)
 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:521)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:712)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
 at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
 at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
 at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
 at com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
 at java.lang.Thread.run(Thread.java:534)
 
I know it's a longshot, but anyone have a clue what might be wrong? Apex is configured to access the apex_fop.jsp as well. and everything is unzipped where it should be and all that.
 
Could it have something to do with the java version or anything?
 
Message was edited by:
p950jbg
Whoops a lil bit messy text 
Thank you in advance 
 
Sincerely 
Johnny
Message was edited by:
p950jbg

Small update again,
I skipped using the downloadable oc4j/j2ee and tried using the one that came with 10.2.0.1 installation (patched to 10.2.0.3)
It starts up fine saying:
07/03/28 21:31:27 Oracle Application Server Containers for J2EE 10g (9.0.4.1.0) initialized
It started up all well with the downloadable latest containers too, but got different errors running the apex_fop.jsp file.
well with the version that came with the database it says in the PDF file after I tried to generate it from a report:
Error 500:
java.lang.UnsupportedClassVersionError: Bad version number in .class file
Anyone got any idea?

Calling dialog program from report

Hi All,
I need to call dialog program from report and do not want the initial screen to be shown and execute the dialog program. can this be possible, if yes please let me know this to do this, when I tried using leave to transaction its showing the initial dialog screen.
Thanks in advane
jog

Hi,
Create a Z trnsaction Code for the Transaction you want to call.
Go to SE93. Give Transaction name and click on create.
Select start object as 'Transaction with Variant' or 'Transaction with Parameter'.
On second screen give transaction name and check the check box for 'Skip initial screen'.
Find out the initial screen for the transaction and mention it.
Now, you can call this Z transaction in your program.

Calling pop up screen CRM UI from BADI

Hi,
I have a requirement to call a pop-up screen in CRM UI from a BADI. The scenario is like:
Whenever a new account in created through CRM UI, a duplicate check has to be done using BADI. If any similar entries found these entries are to be displayed in a pop-up window in CRM UI. As I am new to CRM 2007 please help me in implementing this.
Thank you,
Rregards,
Renjith

Hi,
Try to use CREATE_POPUP or POPUP_TO_CONFIRM method of IF_BSP_WD_WINDOW_MANAGER interface .
Regards
Gaurav

Calling a css user created method from jspx page in ADF faces

Hi all,
Can anyone help me out to solve an issue calling a css user created method from a jspx page.
Note: The css method is not the default css method. It needs to be called using 'styleClass' attribute in any tag.
Thanks
Neha

Hi,
I am not an expert in CSS so I don't know what a css method is. However, CSS can be applied to components via EL accessing a managed bean that returns the sytle text
Frank

Calling graph from Reports created in graphics builder?

Can you call a graph from Reports 6.0 that was created in Graphics Builder. I know you can call a graph from Forms. I tried creating my graph right in Reports with the wizard but for some reason it does not give me the fields I want to use in the available fields column, so I created the graph in Graphics Builder. Do you use a trigger of some sort. Any examples would be appreciated if this is possible. Thanks

Justin Beno:
Yes, you can call a graph from inside a report. All you need to do is select the button with the graph on it (not the icon with the wand, which indicates chart wizard). Then draw graph in the area of the report where you want the graph to display. After completing this, right click on graph, select Property Palette, Chart - Chart Filename (this is where you will type in the directory and filename of your graph that you created in Oracle Graphics).
~Vannette

Call DBAdapter created in JDEV from Eclipse?

Hi
I tried to call dbadapter created in jdev from Eclipse. It gives me the following error:
Server returned HTTP response code: 502 for URL: http://localhost:9700/orabpel/xmllib/ws-addressing.xsd
Any say?
A schema is automatically created and I think it refers to failure to read that schema.
How to resolve this issue?
Message was edited by:
bstn

Hi bstn,
a) is your bpel server running
b) what youar are trying to call? a wsdl?
thx clemens

Pop up dialog async call and forget

Hello,
I do not really have experience with dynamic VI calls, so I would like to ask for some help.
Here is a (screenshot only) part of my MAIN VI, where I call a pop-up dialog VI using the "dynamic call and forget" method:
I only pass one reference into this VI, the ref of the pop-up button, so when the user closes the pop-up window, I re-enable this button on the MAIN front panel. This pop-up dialog functions as a Graph monitor, it can update its Graph using an ActionEngine which is a buffer. So please ignore the missing type defs and the ActionEngines, they are not relevant in this case. Find this pop-up dialog attached.
Actually my application just works, I only started to get some problems since when I included the "MGI Save & Restore Settings.vi" in this pop-up dialog, in order to save Graph settings to a config file (the application will be used as a built exe). When I close the pop-up VI, I can see the Graph settings are properly saved into the *.ini file under the "Documents" folder. However, when this file exists already, and I call this pop-up VI, I get the following error (so when the MGI VI is fired with the "Restore" action at the beginning of my dialog VI):
I have three questions:
What I do is it OK? I mean to pop-up such dialog, is it OK to use the "call and forget" method?
When the user closes the panel of the pop-up VI, does it stay in the memory? Do I have a memory leak, or it closes properly? (I think not...)
I do not understand the error produced by the MGI Toolkit VI, it has something to do with the dynamic call method? I even feed it with the static VI reference of the pop-up VI itself. Before I tried the "This VI" reference constant, but getting same error.
Edit1: hmm, maybe the MGI toolkit is not compatible with Graphs with multiple Y-axis?..I will test it...
Solved!
Go to Solution.
Attachments:
popup_Graph_dialog.vi ‏46 KB

Sam_Sharp wrote:
A few points I noticed:
- Using the call and forget method for launching custom dialogues is fine and something I do quite often - you just need to make sure that your called VI will shutdown correctly when your application closes (if they leave the dialogue open and close the software, for example)
If you have a look at the attached VI, if the user closes the FrontPanel by the "cross at top right", the VI will finishes running, yes? If this dialog is open when the user closes the top level MAIN VI, how should I check it and close the pop-up VI? I could maybe check if the dialog is open via an invoke node? So maybe the best would be not to close the VI Reference after the dynamic call, but store it in a shift register, so I can use it later...hmm, I am not sure what is the most simple thing here...
- I usually use a Strictly Typed Static VI reference (right click the Static VI Reference) for getting the name/path and the VI Type Specifier - it makes sure that your ACBR node always matches the VI you're calling and cleans up the block diagram slightly
I will try this.
- The references you're passing into the MGI functions: "This VI" is definitely the right reference to use as it returns the reference to the clone/instance of the VI that's running rather than a Static VI reference which refers to the Original VI. In your case you can only have one instance of the VI running (because it is non-reentrant) so I don't think it matters here (but I'm not sure?!). I think this will fix the issues with the MGI functions.
Hmm, me neither sure what is going on But I already used the "This VI" constant, and the error was the same. Anyway, I try again, maybe I cannot remember
- I also suspect an issue around closing the VI reference after the ACBR node and having a non-reentrant VI but I usually use reentrant VIs and allow multiple calls so I'm not exactly sure of what happens in the non-reentrant case.
As the first point, I will only close this ref when I quit the MAIN application.
Thanks for the suggestions! I will post back. (i hope using bold is OK

If I create a contact from my call register it does not show up in the contacts on my i phone but does show up in my i cloud contacts. Has anyone else had this happen?

If I create a contact from my call register it does not show up in my contacts on my Iphone but does show up in my icloud. Has anyone else had this happen?

Are you sure iCloud is turned on and that contacts is also turned on (Settings>iCloud) on the iPhone? Be sure the iPhone is not set to Airplane Mode.

How can I Create custom pop up dialog box with question/answer

I need to create a pop up dialog box that asks a question and accepts an answer input. The form needs to be able to be emailed out (not server based) Can someone help me do this? I am a designer, with very (Very!) limited coding skills. Looks like the windjack program that I keep running into does not work with Acrobat X.
Thanks for any help you may have

I am not able to help you with the current method you are using - which seems an odd one in that you are using a menu script to do this????
I would have done the page completely differently - instead of slicing it up into a vastly complex table, I'd have added the image to the page and then used an imagemap. Then I'd have used this script to add the popups (as toolitps) that you can be as simple or as complex as you wish: http://boxover.swazz.org/.
E. Michael Brandt
www.divahtml.com
www.divahtml.com/products/scripts_dreamweaver_extensions.php
Standards-compliant scripts and Dreamweaver Extensions
www.valleywebdesigns.com/vwd_Vdw.asp
JustSo PictureWindow
JustSo PhotoAlbum, et alia

Create shape pop-up dialog box

I am trying to determine what I perceive as a quirk in the Draw Shpe tool (Rectangle, Ellipse, etc.). Usually, I touch the tool, draw my shape and... done! But occasionally through some accidental mouse-motion that I cannot determine, I get the shape plus the pop-up dialog shown below. Can anyone tell me
What mouse-movement, apparently just as I have completed the shape, is bringing up the dialog box?
Is there a way to prevent this from happening in Preferences?
Is this new to Photoshop CC? I have been a casual Photoshop user since Version 2, but I have only seen this in CC, and then, only in the last month or two.
Thanks to all who can shed some light!

I solved the problem, and, as it turns out, it had nothing to do with Photoshop, but rather with a mouse that had started to go bad. I replaced the mouse and all mouse-motion behaviors returned to normal.

Call items are not created for Org BP's when created from Campaigns

Hello All,
We are creating Campaigns for Org BP's and pushing them to channel Phone, which is creating call list but call items are not created for Org BP's.
Org BP's are maintained with Contact Person's, callling hours and phone number are maintained against contact person BP, but still call items are not created with in call list.
Please let me know if I miss any further steps.
Thanks,
Raj.

Hi Debasis,
You can delete the PDS by using /SAPAPO/CULL_RTO_DEL - Delete Production Data Structure . And recif the it to APO. You can use CURTO_CREATE for it.
For the error message /SAPAPO/OM_ERROR2 119 there are couple of OSS notes please check the same.
1648558 - CIF error: 'Mode linkage problem with primary resource'
1325227 - PDS-EXP: Mode linkage problem with primary resource
Regards,
RBrahmankar

Please help!! How to communicate between applet and pop up dialog box

Hi friend,
I have done a AWT pop up dialog box from Applet. In this pop up dialog box, I want get user name, and display on an Applet, anyone can tell me how to do? Thanks a lot!!!!
Alva

You need to create two methods in your applet, getName and setName as well as a name field.
private name = "";
public void setName(String n)
    name = n;
public void getName()
    return name;
}The various constructor methods for Dialog already take the owner of the Dialog (your applet) as a parameter, so in your applet's ActionEvent handler, all you have to do is call
    name = textName.getText().trim();
    owner.setName(name);Yes, it's that easy.

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...

Call Pop-up Dialog created in SE51 from report

Similar Messages

Maybe you are looking for