I did that first thing, did not help. I did put in a new server last
month with a two Tera byte hard drive spinning at 5900 rpm, rather
than the 1.5 Tera byte spinning at 7200 rpm.
Dan Angcao
Micro Design
Computer Consulting
On Mar 19, 2010, at 11:26 AM, "Heffelfinger, Duane"
<[email protected]> wrote:
You might UNLOAD ALL and rebuild the database to see if the database
itself has any issues.
Duey
From: [email protected] [mailto:[email protected]] On Behalf Of
Rachael Malberg
Sent: Friday, March 19, 2010 12:51 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Access Violation
----- Original Message -----
From: [email protected]
To: RBASE-L Mailing List
Sent: Friday, March 19, 2010 12:44 PM
Subject: [RBASE-L] - Access Violation
I'm having a weird problem... I have a database that is just under
one gig. It has an order screen with multiple tables. The system
keeps locking up with an access violation error. This happens at
random. I've been watching the users to see if there is any pattern
to the lock ups but there does not seem to be any. I've checked my
variables to make sure that they anytime a variable is set it has
the data type in the set command. I've all so gone though and made
sure that the variables where clearing after each eep. I was
wondering if anyone else has ever had something similar and what
kind of fix that you may have found.
Thanks.
Dan
PS. Windows 2003 Server
Rbase turbo 8.0.18.30919
