So any idea WHY when you add a 'Stored Procedure' (aka 'SP') that would cause my issue. Name "pcBlackSmith" for the 'SP'!
I have reloaded - unloaded - RScoped - HEX editor - I have so many copies I! I just decided to take my good database and rebuild. (yep - Total unload all and run.all NO errors!) and add a 'SP' and Bang! Errors! How is this connected to LOB's? Ok I see the 'sys_proc_src ' and it appears fine. If I delete this 'SP' I can add a bit button! In this 'SP' is : Switch (.Numbr) case 1 set var v1 = '1' break case 2 set var v1 = 'KL' break endsw return Bad grammar? I am so..... puzzled Paul From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, January 21, 2009 5:18 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Memory Access Error Do you have a backup copy of your database anywhere? Hopefully multiple older copies? If you do, and you haven't done many form changes, I would delete all your rows from sys_forms3 and bring in form data from one of your backup copies. If you know some forms have changed, unload those forms separately before you delete all rows, bring in the backup, test it, and if it works then bring in the separate forms. Karen First and foremost THIS is NOT a RBase problem but mine. So this is a what would you do question? I have "Packed" &"Reloaded" this database and I get a memory access violation in forms when adding a "Bit Button" I know it is MY database because a used RRBYW14 without issues and I used the same procedure on earlier copies (backups) without problems. Just this copy (working of course) has the problem. I know when I do a RScope it will show me the problem I am sure but I've been down that road before. I know it is in the form table and lob's but there must be a easy way to rebuild without dumping / 'Unload All' the whole database and reinstalling. Any thoughts for a fast in place cure? And without a lot of downtime? Heck at this very moment nobody even knows there is a problem.
