I have encountered an error/ internal limitation in gINT and am wondering if others have had similar experiences and or have a solution
I have a log template that outputs sample pictures 2 per page with captions and boring information in the header. It has worked fine for years. Recently after adding numerous pictures to a log that had printed fine before, the program crashed on output to pdf. The error message is provided beliow
This occurred during generation of gints internal database and before any pages were sent to pdf. I reproduced the error on 2 different computers and with files stored both on the network and on the local hard drive. It appears the error occurs after assembling about 45 bit map files as other borings with fewer files in the same project print fine I had never printed a log with that many before
As a work around I can print the first 20 pages of the log to pdf fine then print pages 21- 40 and append to pdf, then print pages 41-60 and append to pdf and it works fine. This proved it is an internal error/ limitation of GINT rather than a problem with the template, my project file or the file environment.
Can anyone tell me what the internal limitation is (number of files, size of files, length of file path?) and if there is a better solution than my workaround?
Hi Szang,
We have seen this occasionally with a large number of photos and it is recorded in our system for the dev team. The issue is not a strict number of images limitation. I have seen some able to print 100's of photos without issue. Your workaround is the best solution, by printing it in multiple outputs. One other option I have seen is to compress the image files. You can reduce the size of the images fairly dramatically without any noticeable degradation of the image for print or pdf purposes, but that requires more work and there would be no guarantee that all of them would output in one pass, but it might allow more at a time or all. I will put an update in the issue for our dev team with your screenshot of the error. It is most likely a size issue of the internal output and not something that can be calculated by looking at the total size of all the images as many other things on a report add to the internal output size not just the size of the final file (ie pdf).
Thank you for the feed back