If the RBase.cfg is in the %OS%\ or \%OS%\System32  (the usual location I
recall) directory I believe you can still use the -A as long as you are sure
the OS has set the path by default (most of the time this is done and Ok, by
Windows Settings) So I would say dup RBase.cfg or outdated/dup dll's.

 

Nothing like the RBase trying to handle two copies and one outdated.  I know
in the past there was a hierarchy to the search of called dll's, cfg, etc..
It was in the order of %Path% then current folder.  Com,Exe,Cmd,Bat, etc..
first  batch files second, etc..  Someone my chime in and let us know how
much of this is true and the current standard.  However I believe you may
have a dup dll in your current folder where you are calling RBase.exe -a
from and the two versions are hitting heads so to speak. JM.02  I hope this
helps.

 

 

 

 

 

Sincerely,

Paul Dewey 

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of MDRD
Sent: Wednesday, September 30, 2009 12:35 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Access Violation errors

 

Paul

 

I think I figured it out,  I remembered I added the -A option to my Icon and
that may have messed up

RBase finding the CFG file, so I dropped the -A and it seems to work.

 

I was getting to smart for myself I guess, there must be something with my
setup for that to happen.

When I get more time I will track down the CFG files to make sure they are
not a problem too.

 

Thanks for pointing my in that direction

Marc

 

 

From: [email protected] 

Sent: Wednesday, September 30, 2009 9:27 AM

To: RBASE-L Mailing List <mailto:[email protected]>  

Subject: [RBASE-L] - Re: Access Violation errors

 

Recreate your RBase.cfg and delete any other rouge copies. 90% of the time
it works for me on those AV errors. 

Good Luck


Paul D 

Sent from my Verizon Wireless BlackBerry

  _____  

From: "MDRD" 
Date: Wed, 30 Sep 2009 09:16:50 -0500
To: RBASE-L Mailing List<[email protected]>
Subject: [RBASE-L] - Access Violation errors

Hi

 

Lately I have been getting Access Violation errors.  Never in the same place
but it seemed like when a form

was loading I would click on a button before the form was fully loaded and
that may have been causing the

error.

 

Today I have gotten 5-6 in a row when I shut down my app and RBase.  I run a
RBA file that takes me to a main

menu form (regular form) then exit that back to the RBA, close the RBA, then
close RBase and the below errors

happen.

 

One recent change a month or so ago was I added the Property clean scratch
files on Exit from the RBA.

 

I wonder is my scratch files / folder are messed up or something?  I
rebooted, started my App, the RBA file, closed

everything again and got the error.  One time I deleted the Property command
to clean the scratch files and did not

get the error but got it the second try.

 

Am I the only lucky one or has anyone seen this before?  I am going to try
to clean out the IE temp files and all Windows

temp files and see if that helps.  This app is basically the same one I was
using in 7.5 and the only change I can think of

is the scratch thing, I was using C:\Temp for the scratch files under 7.5 

 

When I shut down RBase 76 I just started getting an Access Violation error.

 

Access violation at address 00404587 in module RBG76.exe  Write of address
000000000

or

Access violation at address 00406095 in module RBG76.exe  Write of address
000000284

 

I get RBase shut down, but it stays on the tool bar, I have to right click
on it to close it and I get

another error

Exception EAccessViolation in Module RBG76.exe at FFFFF00C

Access Violation at address 000000000C Read of address 000000000c

 

 

Thanks

Marc

 

Reply via email to