Hi Javier,

I'm working with a copy.  I've tried deleting both rows and even though
RScope no longer reports the problem, the Access Violation Messages
continue...

Claudine

> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Javier
> Valencia
> Sent: Saturday, March 19, 2005 12:33 PM
> To: RBG7-L Mailing List
> Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 table
> corruption
> 
> Hi Claudine:
> Whatever you do...backup first!!!
> Then you can try deleting the offending items and see if that fixes the
> problem; if it does not, you still have the original...
> Javier,
> 
> Javier Valencia, PE
> President
> Valencia Technology Group, L.L.C.
> 14315 S. Twilight Ln, Suite #14
> Olathe, Kansas 66062-4578
> Office (913)829-0888
> Fax (913)649-2904
> Cell (913)915-3137
> ================================================
> Attention:
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material.  Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender
> and
> delete the material from all system and destroy all copies.
> ======================================================
> 
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Claudine
> Robbins
> Sent: Saturday, March 19, 2005 12:24 PM
> To: RBG7-L Mailing List
> Subject: [RBG7-L] - Access Violation Messages and Sys_Layouts3 table
> corruption
> 
> Hi all,
> 
> We had a small surge at the office yesterday and one of my db's is now
> constantly giving off access violation messages which cannot be resolved.
> 
> Upon running RScope 7.5, I find that there is an error in my sys_layouts3
> table which cannot automatically be fixed because it contains a note
> field.
> This table has two rows, one for an existing 'important' table, the other
> for a view which I can easily delete and recreate.
> 
> What should I do?
> 
> Claudine

Reply via email to