|
|
|
Re: Printer out of memoryThis error occurs for a couple of reasons only. There is no captured printer port. MEM is too low. Corrupt Printer driver or, drum roll please, you need to reindex or zap the cmsrunnin.dbf file. This is the 3rd file that is on the main menu reindex screen. I prefer a zap in uticms. For the report writer hard core buffs this is the file where ri_param comes from. AWhat this does is clear this file out. If the user never reindexes the main menu evry report that they have ever printed builds a record line in this file. This can create a very large data file. Zapping does nothing to the functionality of the reporting because each report has the ability to have new dates ect for parameters. Each new report then fills up the file. Therefore zapping it empties the file and eliminates the need for it to load to printer memory to be sorted for the correct parameter info at the time of printing. You might also need to force a w2w conversion to make sure the datafiles are lined up. The first thing I will do on these types of errors is to look at mem and if it is too low bring it up. REM the cd rom statement and decrease the buffers statement from 50 to 20. Then a must is to zap the file. Try it. If that does not work look at the captured printer port and or a new driver. |