Thank you Karen I believe that is it! ;)
I just could not find the right name of the sys_forms3 table and recall the table. I would hate to ruin my day and touch upon the wrong item. Sincerely, Paul Dewey Any offers on a video of a tower being hit with a M-14 or S&W 500? New Horizon Interlock Inc. New Horizon Safety Diagnostics Inc. www.interlockinfo.com Saving Lives - One Breath at A Time T This e-mail message is intended only for the named recipient(s) above and is covered by the Electronic Communications Privacy Act 18 U.S.C. Section 2510-2521. This e-mail is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you have received this message in error please immediately notify the sender by return e-mail and delete this e-mail message from your computer. 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.
