Unable to convert the multiple PS files to pdf
Hi
I have distiller server 8 version we are unable to convert the multiple ps files to pdf.
Here is the ps code:
/prun { /mysave save def % Performs a save before running the PS file
dup = flush % Shows name of PS file being run
RunFile % Calls built in Distiller procedure
clear cleardictstack % Cleans up after PS file
mysave restore % Restores save level
} def
(H:/705819_test.ps) prun
(L:/Instruction sheet.ps) prun
(H:/705820.ps) prun
When we run this combine ps through acrobat distiler it is fine, but through distiler server i couldnt get the pdf
Could any one check and help me.
Regards,
Vinoth
We couldnt convert the ps to pdf via distiller server?
Similar Messages
-
I am unable to convert a Quark 9 file to pdf. Any suggestions?
I've tried everything I can think of. It's a 340 page book with maps. I'm exporting it at 72ppi, but it may be that the maps are too large,
Hi there largepdf,
How large is that PDF? There is a 100 MB file-size limit for uploading files to the ExportPDF service. Even if the file is smaller than that, its complexity are your Internet connection speed can also affect the upload/conversion. If the file is overly complex (for example, it has a large number of pages), then it's possible that the ExportPDF service is timing out.
If the PDF wasn't created from a scanned document, and doesn't require text recognition, you may have better luck converting with OCR disabled, as described in this document: How to disable Optical Character Recognition (O... | Adobe Community
Another option is to use Acrobat, which you can try for free for 30 days. Please see www.adobe.com/products/acrobat.html.
Best,
Sara -
File-idoc Unable to convert the sender service to an ALE logical syste
Hi experts
iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
"Unable to convert the sender service to an ALE logical system"
i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
the connection is ok. but still i could figureout the problem.
please suggest me
Thanks
vasaviHi,
Have u checked the logical system is added in the Sender Business service in the Integration Directory?
Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
then specify the logical system name.
Go throgh the following link
Troubleshooting File-to-IDOC Scenario in XI.
Regards
Sridhar Goli -
Unable to convert a ms word file the a pdf
unable to convert a ms word file to a pdf file.
Hi haxbla611,
I am happy to help, but need to know a little more about what's happening. Are you have trouble logging in, or trouble accessing the Adobe PDF Pack online service?
I look forward to hearing back from you.
Best,
Sara -
Setting Font for converting multiple text files into PDF using VB 6.0
Dear All,
Am converting multiple text files into PDF using VB6.0. Currently, am unable to control the font face and size for the generated files. Below is the procedure am using for each file;
Public Sub proc_convert_to_PDF(srcFilename As String, destFilename As String)
Dim p_AcroApp As CAcroApp
Dim p_VDoc As CAcroAVDoc
Dim p_DDoc As CAcroPDDoc
Dim IsOk As Boolean
Set p_AcroApp = CreateObject("AcroExch.App")
Set p_VDoc = CreateObject("AcroExch.AVDoc")
Call p_VDoc.Open(srcFilename, "")
Set p_VDoc = p_AcroApp.GetActiveDoc
If p_VDoc.IsValid Then
Set p_DDoc = p_VDoc.GetPDDoc
' Fill in pdf properties.
p_DDoc.SetInfo "Title", Format(Date, "dd-mm-yyy")
p_DDoc.SetInfo "Subject", srcFilename
If p_DDoc.Save(1 Or 4 Or 32, destFilename) <> True Then
MsgBox "Failed to save " & srcFilename
End If
p_DDoc.Close
End If
'Close the PDF
p_VDoc.Close True
p_AcroApp.Exit
'Clear Variables
Set p_DDoc = Nothing
Set p_VDoc = Nothing
Set p_AcroApp = Nothing
End Sub
What I need;
1) to be able to set the font face of the destination file ( destFilename)
2) to be able to set the font size of the destination file ( destFilename)
Am using Adobe Acrobat 7.0 Type Library
Kindly Help.
Thanks in advanceWe didn't say it doesn't work. We said it isn't supported.
There are a number of other ways to make a PDF. The one which would
give the most control is if your application directly printed to GDI,
controlling the font directly. This could print to Adobe PDF.
You could look for an application that gives control of font for
printing.
You could use a text-to-PostScript system and distill the result. You
could even look for a non-Adobe text-to-PDF.
Working in the unsupported and dangerous world you chose, the font
size for text conversion is set (and this is very bad design from
Adobe) in the settings for Create PDF > From Web Page. There is no API
to this.
Aandi Inston -
Unable to convert the sender service to an ALE logical system
Hello,
file adapter > XI 3.0 > Idoc adapter > r/3 system
In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI > idoc scenario to this same r/3 system (using same sld business system)
I read other topics on this error but it seems they all talk about an IDOC outbound interface.
What should I check?
Thanks
BoazI do have the same problem as Boaz Paz
When I try :
file adapter > XI 3.0 > Idoc adapter > r/3 system
> This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
I get an error while XI tries to call its IDoc Adapter:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>AwayOrders</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
With the following trace logs :
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = AVTItalie</Trace>
<Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
2. declare "AVTItalia" as a business partner in SLD with the logical system name
Plz help! -
Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil. -
Unable to convert the sender service PPG to an ALE logical system
Hello all,
maybe anybody can help or give me further information.
I have set up a scenario to send IDOC from a business system ( ERP ) to a business service ( EXT ).
Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
The send-process is so far ok.
Here my tests:
1) exclude the specific IDOC in IDXNOALE table ( means no technical acknowledgment for this IDOC )
result :
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: not in use
b) message in RWB-Monitor: Sender ERP --> Receiver EXT ok
2) But I would like to have a system status..... here now the problem
add specific IDOC into IDXNOALE table ( for request acknowledgments )
result:
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: acknowledgment not possible
--> error message: unable to convert the sender service EXT to an ALE logical system
b) message in RWB-Monitor: there are now two message,
first: Sender ERP --> Receiver EXT = ok
second: Sender EXT ---> Receiver ERP = system error
Receiver-Interface is : http/ww.ahlstrom.com/EXT/ MI_IN
3) furhter tests:
a) change FTP apdapter channel ( put some wrong settings )
message in SXMB_MONI: status-flag: processed, acknowledgment-flag: contains system errors
message in RWB-Monitor 3 messages ( one ok, and two error messages )
b) changed only the receiver communication channel to HTTP ( other extisting scenario )
then the acknowledgment works fine wihout errors.
I'm wondering, but here Receiver-Interface is: http://sap.com/xi/xI/Message/30/Acknowledgment
Summary: The process works, but strange:
message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
message in RWB: system error
No problems with HTTP adapter
Regards,
Reinhard DoekerHi,
Addition to the above said by Udo...
for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
Check the above link section 3.2
HTH
Rajesh -
Problem Unable to convert the sender service to an ALE logical system
Hi to All..
I'm facing a problem in one scenario File to Idoc .. I got this problem
"Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Also I have another scenario in other Software Component Version SCW and the Idoc works correctly..
I wonder if I miss something
this the trace
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service Sys_XXX</Trace>
<Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Edited by: Luis Ortiz on Jan 25, 2010 3:37 PMHi,
in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
Regards,
Michal Krawczyk -
Unable to convert the sender service to an ALE logical syst
Hi,
My scenario is IDOC to File.
SLD:Configured Correctly ,ABAP Business System.
Imported the same in ID,under Adapter specific Identifiers gava the Logical system as in WE20.
In the Receiver Agreement,Header mapping tried giving the sender service,Receiver service.
Still the Error "Unable to convert the sender service to an ALE logical syst" is seen in SMQ2.
The file is getting generated at receiver directory mentioned in the receive CC.
There is no error seen in SXMB_MONI.
Did any one had a problem as this.
Thanks,
SrinivasaHi,
You need to specify the Logical Name of Business System under Adapter specific identifiers for your Receiver Business System.
The specified item was not found.
Secondly you can use Header Mapping in Receiver Agreement. Or
If you are taking your control records from payload then tick the check box "Apply Control Records from Payload".
Regards, -
Unable to convert the sender service
Hi,
On my new system XI 7.0, I try to configurate a simple "File -> Idoc" scenario without BPM, but I have still a classical dump:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
Note: My Business Service's (of ECC) doesn't appeared between "sender service" and "to an ALE".
Moreover, in my payload, my IDoc has an <u>EMPTY</u> EDI_DC40 segment. Is it normal ?
I have checked:
1) the Logical System name in the SLD
2) the port definition in WE20 compared to this one of CC
3) the RFC destination in SM59 compared to this one of CC
4) the Adapter specific identifier of my Business System
5) then played with sxi_cache...
I'm a few dissapointed... I beleived to have check everything. Maybe not!
MickaelHi Udo,
Here's the result:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>EDB7E1C839603FB9B04057583BE29980</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>BS__TESTXID_1</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>ECB_BS_MDT720</SAP:ToServiceName>
<SAP:ToInterfaceName>DEBMAS.DEBMAS06</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">ECB_BS_MDT720</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCR_ECBMDT720_IDOC</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>interfaceVersion</SAP:Name>
<SAP:Value>3</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passControlSetValues</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passReceiverValue</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passSenderValue</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>SAPECB</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>queueing</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>restoreOriginalParty</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>rfcDestination</SAP:Name>
<SAP:Value>ECBCLNT720</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sapRelease</SAP:Name>
<SAP:Value>640</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>segmentVersion</SAP:Name>
<SAP:Value />
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
it seems it's ok: receiver, sender, port, rfc destination are found. But my EDI_DC40 is still empty
<?xml version="1.0" encoding="UTF-8" ?>
- <DEBMAS06>
- <IDOC BEGIN="">
- <EDI_DC40 SEGMENT="1">
<TABNAM />
<DIRECT />
<IDOCTYP />
<MESTYP />
<SNDPOR />
<SNDPRT />
<SNDPRN />
<RCVPOR />
<RCVPRN />
</EDI_DC40>
- <E1KNA1M SEGMENT="1">
<KUNNR>123777</KUNNR>
<NAME1>Adams</NAME1>
<NAME2>James</NAME2>
</E1KNA1M>
</IDOC>
Mickael -
Unable to convert the sender service insertgoods to an ALE logical system
Hi ,
I am trying to send an IDOC to sap system through XI BPM . But I am getting error as "Unable to convert the sender service insertgoods to an ALE logical system"
To rectify this error, I selected the integration process in integration directory and in (services---adapter specific properties I gave the logical system name as "LS" . Now i do not get any error in XI but idoc failed in SAP with error as "Partner profile not available "
Please advice .
Thanks & Regards,
SuvarnaHi Suvarna
I have done this type scenarios using A2A and BPM also. I got success.
Here what i mean to say , forget about your integration process for a while.
For example you are sending a vendor file from System1 to a SAP System (IDOC). Here that file send by sender should be converted into IDOC.
So during the configuration of SLD for Sender system ,we should give logical system (any name) for Business System.
That logical system should be created in SAP system in (SALE tcode).Then you can't get that <b>"Unable to convert the sender service"</b>error.
For integration process no need to assign any logical system , leave it blank.
If you have any doubt you please call me on my mobile or give me your mail id I will forward the document which i have done.
thanks
Prasad 9960226467 -
File2IDoc Scenario-Unable to convert the sender service to ALE logical sys
Hi,
I've created a simple file to idoc scenario. my fileSender was defined as sub-element of "Business Component". when i tried to test i got the err:
"Unable to convert the sender service SandBox_File2IDOC to an ALE logical system"
in order to workaround the issue i had to re-create the fileSender as sub-element of pre-defined business system.
as far as i understand, idoc sender should be part of (i.e., sub-element) of business system. - my first Q: "am i right?
second Q: in case this is the correct way to solve the issue, should i define (as part of sld definitions) a new dummy business system?
Regards,
UriA very common problem and a standard solution:
Make sure you have entered the logical system in ID :business system --> Service --> Adapter specific identifiers.
If you need more help, refer the following links:
http://wiki.sdn.sap.com/wiki/display/XI/UnabletoconvertSendersystemtoALElogicalsystem
Unable to convert the sender service to an ALE logical system -
Unable to convert the sender service ACC_BSer_SEN_F2I to an ALE logical sys
IN a File to Idoc senario.... this the error am getting , wot may be the issue
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>ACC_BSer_SEN_F2I</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service ACC_BSer_SEN_F2I to an ALE logical system</SAP:Stack>Hi Kiran,
>> <i>But here the issue is, i did not get my IDoc created in R/3 side.</i>
What is the status of ur idoc in the R/3 system? Go to we02 or we05 and check the status of ur idoc that u have sent to idoc.
>><i>Do we need to send the data in the specific R/3 format?</i>
Yes.The R/3 will receive data in specific format either it may be via idocs,RFC's or proxies.
>><i>Inbound Message ( CENTRAL ) - Green flag
Response - Black success flag.</i>
It tells that the msg in moni is successfully.
Regards,
Prasanthi. -
Converting Multiple .EPS files into .PDF
Dear Forum: We have tried converting multiple .eps files into PDF using article 325977. This article in Adobe help is really designed to convert .ai files into either .eps or.pdf, our situation is to convert multiple .eps files into PDF. Everytime we run the macro, it simply takes the eps file and saves it as another eps file and does not convert. We have a "Save As" step that we have in the macro that is set to "Save As" PDF, but it still does not work. What are we doing wrong?
Hi mephisto11757,
You can convert the following file types to PDF with the Adobe CreatePDF service:
Adobe Creative Suite® file formats Examples include: .psd, .ai, .indd
Microsoft Word (2000, XP, 2003, 2007, 2010, & 2011) .doc, .docx
Microsoft Excel (2000, XP, 2003, 2007, 2010, & 2011) .xls, .xlsx
Microsoft PowerPoint (2000, XP, 2003, 2007, 2010, & 2011) .ppt, .pptx
Microsoft Publisher (2000, XP, 2003, 2007, 2010, & 2011) .pub
Text Files .txt
Rich Text Format .rtf
Adobe PostScript .ps
OpenOffice Format .odt
Star Office .sxw, .sxi, .sxc, .sxd, .stw
Corel WordPerfect .wpd
Image file formats .gif, .png, .jpg, .bmp, .tiff
Regards,
Florence
Maybe you are looking for
-
How to get values from a table(in jsp) for validation using javascript.
hi, this is praveen,pls tell me the procedure to get values from a table(in jsp) for validation using javascript. thank you in advance.
-
Help! DVI to Video adapter not working!
Hello, I bought a brand new DVI to video adapter and it's not working. I plug it in and it shows the start-up screen, but it's split screen and it's in black and white. Then, it goes into the black and white lines, not showing what's coming out of th
-
I have written a function in one of my reports. I get the error message "Element ST_ADDR is undefined in ADDRESS." when I try to run the report. My funtion looks like: <cfargument name="ss" required="yes"/> <CFSET variables.BoxNo = ''> <cfquery name=
-
How to use GR55 and Report Painter in SAP?
Thanks and regards, Sudhajiban
-
Khmer Unicode font run error in adobe presenter 7
I really don know why adobe cannot run well and have many problem like this , would you like help me this case i need solution .i will send to you this by the original file that i not yet publish and file that i publish ready . do you see ? when i pu