Unanswered: Printing Problem "Run-Time Error" '482'
Hope someone could assist me.
I thought It might be the old computer so I bought a new one: I7 16gig mem and with 2Tb HDD. Printer: Aficio MP C 2800
I also bought the upgrade BD 10.54 a few months ago and using BD as from 2007.
When I printed 20 pages it works fine but when I tried to print let's say 178 pages it gives me a printer error "Run-Time Error '482' and then exits the DB. I tried to print PDF but it then completes the printing process up to about 65% and exit's the DB.
When the error occur the printer status is as follows:
Document Name Status Pages Size
Brilliant Database_SDK Spooling 36 16.8MB
It seems to me it's still a memory problem. The Query that I ran before printing is realy simple:
[Campus] = "NET" and
[Current Level] = "2" And
[Current Level] Not Ends with "Attachment"
Because of this I have to break up my printing tasks to lost of small tasks.
I have to print in total reports for 3500 students.
As you know, Brilliant Database is a 32 bit Application, so it cannot address more than 3GB of System Memory.
Doing some tests here, it just so happens that when I run your database, my system memory is sitting at a certain value. When I then run a report, Brilliant Database will crash every single time it's system memory usage plus the amount of data its trying to send to the printer pool hits exactly 3GB.
That seems to be more than a coincidence to me as it will crash every single time dead on the 3GB mark.
I think this is one for brilliant database to look into. Surly the printer pool added to the amount of ram used shouldn't cause this.
Is it maybe possible to write the query with lets say 10 different print jobs and between the jobs "clear" the memory? The reason for this is that even if I print a big file that BD could handle and go to the next print job of the same size then BD crash.
But if I exit BD and go back in the BD will print that file. So it seems to me I have to clear the memory between the print jobs which BD could handle.
I tried to download some tools/fixes to help with the 3gig limitations but without any success.
Looks like a design problem with Brilliant Database itself. The printer engine seems to be not correctly unloaded from the Memory. This can only be repaired by Mikhail.
Good to know, because I am planning a larger application with large print jobs.