Sometimes AV with RB 7.04 in Terminalserver

rbuser

Hi!

One of my customers have the application running with a terminalserver.
And he told me that he sometimes get the following Exception:
----
Exception 'EAccessViolation' in module winmgm.exe at 001B4575
Zugriffsverletzung bei Adresse 04345575 in Modul 'winmgm.exe'. Lesen
von Adresse 0000001D

Source file: ppPDlg.pas, Line 473

Call stack:
:04345575 [winmgm.exe] (ppPDlg.pas, line 473)
:043453F4 [winmgm.exe] (ppPDlg.pas, line 420)
:041E8186 [winmgm.exe] (Forms.pas, line 4275)
:04200BD2 [winmgm.exe] (Controls.pas, line 4227)
:0420430F [winmgm.exe] (Controls.pas, line 5731)
:041E52AB [winmgm.exe] (Forms.pas, line 3063)
:04203E57 [winmgm.exe] (Controls.pas, line 5612)
:041E17D2 [winmgm.exe] (Forms.pas, line 1459)
----
ppDlg.pas, Line 473 is:
if (ppPrinters.PrinterInfo[cbxPrinters.Items[liIndex]].IsLocal) then

I am using D5 with RB7.04. Any ideas what this could be? I am not able
to reproduce this error on my site and my customer get it only 2 - 4
times a week.

Gruß aus den Bergen
Günter

nardmoseley

This is not a known issue.

ReportBuilder caches information about the available printers. Perhaps while
the application is running this information is changing (i.e. printers are
being removed/added on the machine or the user account).


To refresh the list of installed printers, please see the following
article...

-----------------------------------------------
Tech Tip: Refresh List of Installed Printers
-----------------------------------------------


ReportBuilder caches information about the printers installed on a machine.
If you install printers while your application is running and want to
rebuild the printer list, use the following exampe code.


uses
ppPrintr;


begin

ppPrinters.Refresh;


end;



--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

In article <42de6abd$1@dm500.>, Nard Moseley (Digital Metaphors) wrote:

I did this everytime before I print a report (shortly after Loading the Report
from a file) but know I get some curios errors when I try to print. Should
this call be save to do before every .Print?


Gruß aus den Bergen
Günter

nardmoseley

Probably should do it prior to loading the report.




--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com