If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Access XP CRASH!! on opening VBA Editor Or Modules
what else can I do? Once "/decompile" worked for me, but now it does not help
anymo I have two win2k machines and one mdb-file: in normal daily use the mdb works on both, but the vb-Editor I can only use on one computer. On the other access2K crashes without further notice when I click try to view or edit the code. "Allen Browne" wrote: Great news! No doubt you will be adjusting your backup routines now. During development (when you are changing forms/reports/code), Access does corrupt fairly often, whereas it is extremely reliable once it is developed and only the data is being changed. So during development we make a copy of the mdb file twice a day, so you never lose more than 1/2 a day's work. -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Luke" wrote in message ... Hi Allen, Wow! Can't thank you enough for your help. I was in a bit of trouble there for a while and you've saved the day! Cheers, Luke. "Allen Browne" wrote: No promises, but if it is the binary that is bad, this might work: 1. Decompile a copy of the database by entering something like this at the command prompt while Access is not running. It is all one line, and include the quotes:H "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" 2. Make sure that the Name AutoCorrect boxes are unchecked under: Tools | Options | General 3. Compact the database. Any luck? -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Luke" wrote in message ... Please Help! I have written a lot of code for a database Ive been working on in a fully up to date, legal version of Access XP. Unfortunately, Ive been stupid and havent been creating backups. THE PROBLEM; When I try to open the VBA editor, trigger any code or view any module within the project, access crashes with that terrible message... " Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience." This only happens with the one .mdb file. Ive tried exporting my forms and modules to a new blank .mdb file. This just moved the problem to the new DB. Is it possible to recover my code? What do you think is causing the problem? How do I avoid the same problem in the future? PLEASE HELP! Luke |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Opening Access 2003 files with Access XP? | Jerri | General Discussion | 1 | March 18th, 2005 02:51 AM |
What is the difference between 2002 and 2003? | Red Sonya | General Discussion | 2 | March 1st, 2005 05:10 AM |
Book recommendations, please | Top Spin | New Users | 2 | March 1st, 2005 12:43 AM |
Access 2000 -vs- Access 2003? | Mark | General Discussion | 5 | November 30th, 2004 06:36 AM |
Need help with Access decision | aualias | General Discussion | 23 | June 21st, 2004 02:04 AM |