Runtime printing problems v6.5, 8.0

[mwallace]

Our Network Administrators recently changed out network printers from _Queue based_ to _IP based_ whatever that means. Since the change, when my Runtime users try to print using v6.5, they get the following error: _Printer initialization error _ check available memory_.____I upgraded these users to v8.0, but now there_s a different problem. The reports run properly, and the first page displays on the screen. But if I click the page forward or print buttons, the runtime session ends without printing or displaying. If I click the print current page button, I get a Windows memory read error. Also, the problems with 8.0 are sporadic. Sometimes, reports run okay, then all of a sudden, the above problems crop up.____I am thoroughly confused by these problems. Any suggestions?__

[Sanchosada]

We just solved a long time issue with one client and this may solve yours. If the runtime is from a shared network drive, and multiple people are trying to print. We needed to use the /O parameter to make a seperate RRRUNOUT file for each user.____On a Novell Network, the first client who runs a report seems to work fine, but the next person to run a report sees the first page, but when they try to go to the 2nd page, the R&R runtime closes, and goes back to our program that calls the runtime. This is V8.0 usinf Visual Foxpro 7.0 on a Novell 5.0 Network. We have no problems with this issue on a Microsoft NT/2000 Network.____

[mwallace]

Wow, I didn^t expect anyone to reply after 2 1/2 months! Thanks for the suggestion. We have been having exactly the problem you described, and when I added the /O parameter it did indeed solve the problem, allowing users to scroll freely through their reports.____It did not solve the problem trying to use the Print Current Page button. When my users press this button we still get the Windows Memory Error.____Thanks so much for the help,__Mark____