Willie,
if you cant event track where it is happening, then the easiest way
is to add try/except blocks as follows to all methods..
procedure
begin
try
your normal code
except
raise; // Put break points on each on of these
end;
end;
In fact, I think it should be done by the compiler as standard. :-)
Regards
On 9 Jul 99 at 11:53, Willie Juson wrote:
> I'm receiving one of these when I call the print method of an R-Builder =
> pro ppReport componenet. If I preview the report first it's fine, but if =
> I try to print it first I get an access violation.=20
> How do I trace this? - I've tried "stepping into" the code using the =
> debugger but obviously I need to be a bit smarter. Any comments much =
> appreciated.
>
Rohit
======================================================================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
PH (649) 489-2280
FX (649) 489-2290
email [EMAIL PROTECTED] or [EMAIL PROTECTED]
======================================================================
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
