Using ASPOSE to bundle / stich PDF - Replace ActivePDF toolkit

Aspose.Cells Product Family
1

This is about both whether there is a solution that ASPOSE has, or more ugently if you can resolve an issue we're having with bundling documents converted to PDF by ASPOSE.CELLS, using ActivePDF toolkit.

When we use ASPOSE.cells to generate PDFs of out XLS(x) documents, ONLY these PDFs (and ALL of these PDFs, even generated from a simple document with one number in one cell) are not able to "bundle" together with other PDFs using the ActivePDF toolkit methods.

One reason things don't "bundle" using ActivePDF toolkit is when the PDF has password security on it. When you try to bundle one of these, it just simply gets ignored and does not appear in the bundle.

The same effect is occuring with ALL PDFs generated by ASPOSE.CELLS.

Any ideas would be appreciated! Thanks so much. Dave

2

Hi,

Thanks for your inquiry.

We will get back to you soon.

Thank you.

3

wonderful thanks so much

4

Hi,

Please send an example project of bundling or stitch pdfs using ActivePDF here. We will check your issue soon.
Thank you
5

Hi Sir,

This is the code we are using to call the Toolkit.

set TK = Server.CreateObject("APtoolkit.object")

TKreturnCode = TK.OpenOutputFile(Server.MapPath(dirOutput) & "\" & OutfileName)

dim tempFileName

for intI = 1 to PDFcount

tempFileName = Server.MapPath(array(1,intI)) & "\" & array(2,intI)

TK.ClearHeaderInfo

TK.GetBoundingBox tempFileName, intI

'TK.SetHeaderFont "Courier-Bold", 12

'TK.SetHeaderTextColor 255, 0, 50, 0

'pagewidth = TK.BBWidth - TK.GetHeaderTextWidth(array(3,intI))

'TK.SetHeaderText pagewidth/2, 12, array(3,intI)

TKreturnCode = TK.MergeFile(tempFileName, 0, 0)

next

TK.CloseOutputFile

Set TK = Nothing

We believe the code per se is not the issue, simply because the “bundling” DOES work fine. However, its ANY pdf document generated by ASPOSE.cells that CANNOT be bundled. I will attach a simple one here, which I have already tested/proven does not work - meaning will not bundle together with other PDFs.

Attached is a PDF file generated from a simple excel document converted to PDF with aspose.cells.

PS: Note that word docs generated from Aspose.words do not have this issue.

Thanks!Dave

6

Hi Dave,

Thanks for the template file with sample code.

We will check your issue and get back to you soon.

Thank you.

7

Hi,

Please try the attached version v4.7.1.13 and let us know if it works fine now.

Thank you.

8

Hi, I don't believe i've been able to adequately test due to:

1. When i put this DLL in place of the old one, the xls files don't convert at all anymore. I get a 404.

2. Also, the other aspose products i'm using (words and pdf) suddenly start printing the eval copy notification.

3. When i reverted to the prior DLL, this all wen't back to working as before, though still activePDF toolkit can not bundle pdf's created by aspose.cells still.

Notes:

1. You included a .TLB file in the zip you sent me, I don't know what that is for but i could not find anywhere to place it.

2. In case it is a clue which helps, I went to support.persits.com/pdf/demo_append.asp since persits also has a tool that stitches files. Unlike activePDF toolkit, it DOES work but only as long as at least ONE of the PDF documents i give it was NOT created with aspose.cells. When both were created in aspose.cells, here is the error i get (you can duplicate it i'm sure):

Persits.PdfManager.1 error '800a0039'

endstream word not found. Offset: 331 (Hex 14b)

/pdf/demo_append.asp, line 71

I'm not sure if that helps you but at least its an intelligent error that can be worked with!

Thanks, Dave

9

Hi,

After analyzing your issue, it seems that you didn't register the new version of Aspose.Cells for .NET. Please register it, and have a try then. You need to register the component if you are accessing it as a com client, see the document: http://www.aspose.com/documentation/file-format-components/aspose.cells-for-.net-and-java/accessing-component-from-com-clients.html

For .TLB, it is type library file which describes all the details of the component's types / API etc for the com clients, you may open it into vs.net and get the details.

Thank you.

10

When you say "register" it, do you mean pay for it?

I did!

This is a legit copy of aspose total i just bought it last week.

If you mean something other than that, can you please explain?

thanks, Dave

11

Hi,

filetrac:

When you say "register" it, do you mean pay for it?

No, I do not mean that. Well, I mean you should register the new Aspose.Cells.dll (fixed version provided) on your machine using regasm.exe (.NET utility), you may register the component trying the following command on VS.NET command prompt (i.e.., Visual Studio 2005 Command Prompt in Visual Studio Tools):

regasm Aspose.Cells.dll /codebase

Kindly let us know if you need further clarification, we would be happy to help you.

Thank you.