Bob,

Thanks for the response. I contacted the man on site and asked him to restore 
the DB with last night's backup.
Since no added work was done this morning, there should be no extra work 
involved.
I am off site so I cannot do this myself.

You had mentioned a few weeks back that you have extensive work with BOM setup.
I had sent out a request for help and was able to find a partial solution.
Any help would be appreciated.
I will be off line for a bit this morning but should be back on line once the 
DB is fixed, hopefully sometime before noon.

James Belisle

Making Information Systems People Friendly Since 1990


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Bob Thompson
Sent: Wednesday, December 16, 2015 9:14 AM
To: Jim Belisle
Subject: [RBASE-L] - Re: exception error

Sorry to hear of the issue. 

The message is a general Windows error stating Rbase did something to crash the 
session.  (It may have been an external cause, but it was the Rbase DLL that 
resulted in the message. 

The first thing I would try is to replace the RX1 file if you have a recent 
backup. (Backup all four RX files before you do this). This might fix the 
structure and save your data.  No guarantee though. 


Bob Thompson
LaPorte, IN
219-363-7441

Sent from my iPod

On Dec 16, 2015, at 6:05 AM, Jim Belisle <[email protected]> wrote:

> 
> I received an error this morning that I have not seen in many years.
> Exception EaccessViolation in module RBENGINE95_64.DLL I just got 
> through creating a new table and went to enter information into the table 
> using a form when this happened.
> I am connected remotely. Others at the shop said they just got the same error.
> How will I be able to fix this?
> 
> I have RSCOPE and checked the structure and it showed I had four errors.
> I hit the fix button for the offending table and deleted the table but that 
> did not allow me to get back into my Database.
> Not a good way to start the day.
> 
> James Belisle
> 
> Making Information Systems People Friendly Since 1990 
> [cid:[email protected]]
> 


Reply via email to