Most of the time, my Access Violations are due to trying to follow a pointer with the value of nil. The access violation message will refer to the address 00000000.
Rainer ----- Original Message ----- From: "Roshanak Farhoodi" <[EMAIL PROTECTED]> To: "Borland's Delphi Discussion List" <[email protected]> Sent: Saturday, February 04, 2006 6:39 AM Subject: Access Violation > Dear all, > > I've encountered "access violation" error for the first time when I was > testing a program which has a lot of (really a lot!!!) variables, > assignments and calculations. 2 b more specific, one of the buttons of my > program, has a lot of calculations behind, the user can set some > parameters and then press it 2 see the results of calculations. but the > program tolerates the button 2 b pressed only 3 times, after that "access > violation" exeption will b raised. > May it be concerned with low virtual memory or what??? if it is really > due 2 shortage of virtual memory, when handeling such heavy programs what > is the best idea to manage or free the used up memory? Is there any > "garbage collection" or another similar policy as there exists in JAVA? > > So many thanks in advance 4 ur any comment, > Roshanak F. > > > --------------------------------- > Relax. Yahoo! Mail virus scanning helps detect nasty viruses! > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
