In my experience an Access Violations results in memory being read/written on the users computer by a program it doe not own. In some of my cases it happens on workstations with a low end graphics card that has it's own RAM and is resolved by setting the computer to Performance Mode... (start>my computer, right click, properties>advance tab> performance>setting button>visual effects tab>select adjust for best performance.)
----- Original Message ----- From: TOM HART To: RBASE-L Mailing List Sent: Friday, January 22, 2010 7:29 AM Subject: [RBASE-L] - Re: Access violation I am not running on a network. Tom ------------------------------------------------------------------------------ From: "Walker, Buddy" <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Fri, January 22, 2010 5:32:42 AM Subject: [RBASE-L] - Re: Access violation Tom This happens to me as well. I was assuming it is a network issue. I have a scheduled task (runs every 10 min) that connects to the database and if successful copy the RB1 file. Buddy From: [email protected] [mailto:[email protected]] On Behalf Of TOM HART Sent: Thursday, January 21, 2010 11:17 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Access violation Yes Rbase works on my other databases, it even works on the one I copied to change my label, so its not a big loss but I sure would like to know what happened and if it can be fixed. Tom ------------------------------------------------------------------------------ From: Paul InterlockInfo <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, January 21, 2010 5:42:08 PM Subject: [RBASE-L] - Re: Access violation Tom- Keep us posted. I will think about it some more. Hey does RBase work on another db? Bob- Now that is cool! Replace .rb1 Makes you want to back up every hour verses 3 hours. Sincerely, Paul D. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, January 21, 2010 6:29 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Access violation Caution! make sure you have backups before trying this. On very rare occasion, I have experienced a similar crash. The following worked in my case. If you had not made DB structure changes during your session that crashed, try the following: Copy or rename your existing .RB1 file to a safe location. Copy the most recent back up of your .RB1 file into your working folder. RBSYNC the database. Hopefully you will be up and going. Note that your .RB1 file you renamed/ saved needs to be the same as the backup you restored. I.E. no database structure changes made. -Bob ----- Original Message ----- From: "TOM HART" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, January 21, 2010 5:00:34 PM GMT -06:00 US/Canada Central Subject: [RBASE-L] - Re: Access violation The error messages are set to ON. Tried RBSYNC and said database was already in sync. Tried RECOVER and said not in need of recovery. Tom ------------------------------------------------------------------------------ From: John Minyo II <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, January 21, 2010 4:50:24 PM Subject: [RBASE-L] - Re: Access violation Tom, Not knowing if you have ERROR MESSAGES set to OFF, there may be other details provided to you. Can you verify this is set ON. You may have database files out of sync. The out of sync message derives from the four database files having non-matching date and time stamps. To fix the problem, use the RBSYNC command. If you use transaction processing, which is not likely since you were editing a label, the RECOVER command would fix the database files. John At 05:27 PM 1/21/2010, you wrote: > I was working on a label in 7.6 and all of a sudden I get the: > Access violation at address D1E8728 in module 'RBEngine76.DLL' write of address 4D50203. > I have occationally gotten an access violation but was able to 'control/alt/del' out, restart Rbase and get back to work. > This time, however, I cannot re-connect to that database. I can connect to other databases. Have run Rscope on the problem > database and find no errors. Using the most current update. > Tom Hart
