Bonjour,

NB :

As-tu installé Ghostscript et l'imprimante virtuelle Sybase DataWindow PS ?

En principe le code d'export est comme cela :

int li_ret 

dw_1.Object.DataWindow.Export.PDF.Method = Distill!
dw_1.Object.DataWindow.Printer = "Sybase DataWindow PS"
dw_1.Object.DataWindow.Export.PDF.Distill.CustomPostScript="Yes" 
li_ret = dw_1.SaveAs("custom.PDF", PDF!, true)

Using the Ghostscript distiller
In order for users to use the SaveAs method to save data as PDF with the distiller, they must first download and install Ghostscript on their computers as described in the procedure that follows.

The use of GPL Ghostscript is subject to the terms and conditions of the GNU General Public License (GPL). Users should be asked to read the GPL before installing GPL Ghostscript on their computers. A copy of the GPL is available on the GNU Project Web server .

The use of AFPL Ghostscript is subject to the terms and conditions of the Aladdin Free Public License (AFPL). Commercial distribution of AFPL Ghostscript generally requires a written commercial license. For more information, see the Ghostscript Web site .

To install Ghostscript:

Into a temporary directory on your computer, download the self-extracting executable file for the version of Ghostscript you want from one of the sites listed on the Ghostscript Web site .

See the Release Bulletin for the version of Ghostscript that was used for testing.

Run the executable file to install Ghostscript on your system.

The default installation directory is C:\Program Files\gs. You can select a different directory and/or choose to install shortcuts to the Ghostscript console and readme file.

After installing Ghostscript, you should read the readme.htm file in the doc subdirectory in the Ghostscript installation directory to find out more about using Ghostscript and distributing it with your application.

Save Rows As fails To save as PDF in the DataWindow painter, select File>Save Rows As and select PDF as the Save As type. If you do not install Ghostscript and use the default export properties, PowerBuilder displays a pop-up window notifying you that Save Rows As failed. If you install Ghostscript and then change the name of the directory where Ghostscript is installed, Save Rows As PDF fails silently.



Location of files
When you save a DataWindow object as PDF using the distill method, PowerBuilder searches in the following locations for an installation of GPL or AFPL Ghostscript:

The Windows registry
The relative path of the pbdwe120.dll file (typically Sybase\Shared\PowerBuilder)
The system PATH environment variable

If GPL or AFPL Ghostscript is installed using the Ghostscript executable file, the path is added to the Windows registry.

If the Ghostscript files are in the relative path of the pbdwe120.dll file, they must be installed in this directory structure:


dirname\pbdwe120.dlldirname\gs\gsN.NNdirname\gs\fonts

where dirname is the directory that contains the runtime DLLs and N.NN represents the release version number for Ghostscript.

You might not need to distribute all the fonts provided in the distribution. For information about fonts, see Fonts and font facilities supplied with Ghostscript .

PostScript printer drivers
If your users have installed a PostScript printer on their computers, the PostScript driver files required to create PDF files, PSCRIPT5.DLL, PS5UI.DLL, and pscript.ntf, are already installed, typically in C:\WINDOWS\system32\spool\drivers\w32x86 on Windows XP or C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_1a216484\Amd64 on a 64-bit Vista system. Your users must use the version of these files that is appropriate to the operating system where the PDF file is created. They should copy the files to the dirname\drivers directory.

You must also deploy the related files that are installed in Sybase\Shared\PowerBuilder\drivers. These files can be copied to or installed on users' computers. They must be located in this directory structure:


dirname\pbdwe120.dlldirname\drivers

PostScript printer profile
Each user's computer must have a PostScript printer profile called Sybase DataWindow PS. This profile is added to your development computer automatically when you save a DataWindow's rows to a PDF file in the DataWindow painter. You can use this method to add a Sybase DataWindow PS printer on any computer where PowerBuilder is installed.

Users can also add the profile manually using the Windows Add Printer wizard in one of the following ways:

By clicking the Have Disk button on the Install Printer Software page of the wizard, browsing to the Adist5.inf file (installed with PowerBuilder in the Shared\PowerBuilder\drivers directory) or to another PostScript driver file, and on the Name Your Printer page, changing the printer name to "Sybase DataWindow PS".
By selecting a printer with PS in its name (such as "Apple Color LW 12/660 PS") from the list of printers on the Install Printer Software page of the wizard, and changing the printer name to "Sybase DataWindow PS" on the Name Your Printer page.

See the chapter on the Print Manager in the Deploying Applications and Components to .NET book if your applications print to PDF or XSL files from an IIS server.

On est obligé d'installer GS !!!

Et comment ça se passe concrètement au niveau utilisateur... il suffit que ça soit installé sur le serveur ou faut l'installer sur chaque poste ???

Et quid d'une appli APPEON ???

Comment ça, je suis relou ;)

Merci pour vos réponses...
Dans le doute, j'ai installé GS sur le serveur et j'ai configuré l'imprimante nommée dans vos posts sur ce même serveur.

J'ai testé la création de pdf depuis différents postes et ça a l'air de fonctionner