We have several reports which print at the end of the month that can be quite sizable. The user wants them to go to pdf and so we have done so. The problem is that for small selections (manual for users) the report works fine, but on the monthend it reports on ALL products which comes to a selection of 94K rows. Each row gets approx 6 lines of text.

at 'Page 1 of 4809' blanks vsprinter. It still says 'printing .. ' but the count is no longer growing AND eventually it will say 'cant create pdf' or some such ..

so why is this?? Do we have to purchase something else (pdf driver) in order to get this report to work?

thanks

this really appears to be a memory issue of some type.

I ran the report setting the max page to 4807 and it still died with the 'not able to write pdf file message and resetting display blank with page 1 of 1 (and still printing)

I then set it to only process the first 4000 pages. It generated a pdf whose size is 790,284.

Then set the routine to stop processing after 4800 pages. It completed but the report size is 3,746 (hmm something missing here?)

I tried to open this and get a 'font has not been set' and a blank page (with reader showing page 1 of 3)

opps .. i just tried to open the 4k page process but it comes up with 'font not set' and pages showing 1 of 708.

the small report (multi page) works just fine .. (created 6 pages)

We've normally found this to be a memory issue.

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

There is definitely a memory issue with the vsprinter ocx. It has nothing to do with data, just pages. My machine is about 4800 pages but this can vary based on available memory.

does the ocx have an option to print to disk as it builds?

is there any way around this?

i guess that half a gig and 83gig of free space just isn't enough for oi

Yes, you can print to a pdf writer.

True - but be careful which one you use. Adobe's 3.03 writer (which may be updated now) will change the default/current directory when used and crash OI if you don't put it back after the OIPI call. I believe the print driver in PaperPort does the same. This does not occur if the file is written to the OI default directory (but you know what a mess that can make, over time).

Also, I have noticed some slight changes in output when using a PDF writer – but mostly to the "good", as it did get around some older and mostly fixed problems with OIPI preview then PDF not yielding the same output as printing (to a printer or the PDF driver, both of which were identical results, I believe).

have you guys talked to the people who wrote vsview about this?

also, if i try to use the OI pdf .. is there a way to *know* how large the report can get? as mentioned yesterday .. even though it wrote out the file .. adobe says it isn't any good ..

Still looking for a way to calculate this.

If it writes out without any errors then why are we getting 'font not been set' from adobe .. then all 801 pages are blank ..

It is a 790K file.

How do we guesstimate the size of the file that is allowed?

in follow up .. i created the same file file that breaks in 'pdf' to a text file. the final text file was 28.9meg which is much larger that even the pdf that can't be open (it was 700K).

It would seem that there is a problem with the ocx when using pdf mode.

Dave, it is not a pdf but the preview window that will not handle a high number of pages (4000 to 5000). If you send the print to a pdf printer as 0 or 1 in the init option it should work fine.

thanks man .. will try it to night to the file and see what happens

it is odd that the smaller ones (2000 pages instead of 4800 pages)still say 'no font set'.

will as i said, try it tonight and report back

After re-reading what you said ..

".. If you send the print to a pdf printer as 0 or 1 in the init option it should work fine"

I am assuming that by 0 or 1 you mean of param5

EQU P5_STYLE$ TO 1

*0=Print to printer

*1=Display PrintSetup

*2=Preview normal

*3=Maximized

*4=Last location

*5=Specific location

*99=Print to printer with the WMF Fix

the point is that we need to go to a pdf file .. not a printer .. no user intervention.

option 0 and 1 wont get us therre will it?

in follow up .. it appears that ONLY PDF fails.

I changed type to html & dhtml .. it displayed all the report in the preview AND it created the output file .. as it displayed pages. 105meg file. It appears that after page 4791 (in the dhtml file) it stopped creating. The totals page did not complete

I then changed to a TEXT file. It created all pages to 4801 and that last page contains the grand totals. Total txt size 23meg

So .. it does appear to have something to so with memory .. and we can 'WORK AROUND' the problem for the moment by creating text files .. but i really believe that this should be corrected.

Does this problem happen with the the ocx? does it happen in vb? Does the developer (componentone?) know that there is a size issue? I have found nothing in the sources available on line.

thanks

Yes, this is an OCX issue and it does happen in VB also. Component One has not yet responded to the issue.

cool .. and cool.

We will work with the text workaround until further notice

thanks

Dave,

We don't know when we are going to hear back regarding the size issue. You may want to have a workaround that doesn't create such a large PDF file. Maybe smaller pdf files?

Sean

has the newest version of the control been tried?

View this thread on the Works forum...