Error when I try to find and replace in the VBA Editor.
- Thread starter kwbonin
- Start date
- Local time
- Yesterday, 19:48
- Joined
- Feb 28, 2001
- Messages
- 30,567
Yes, I've seen that in the context of the Internet Explorer.
You, my friend, have found what we call a BUG. {gasp}
Something "impossible" happened to Access that caused a rarely used Windows feature to wake up and take a snapshot of the dying Access application. If you allowed it to do so, this little window you showed us would send a bug report to the folks at Microsoft. They might (or might not) contact you for supplemental information.
You didn't show us the technical information (bottom of the window, one of the two links) so it is hard to know what really happened. But it was probably incomprehensible to anyone who doesn't understand that level of error message anyway.
You might have a bad copy of Access (i.e. need to re-install from CD-ROM) OR you might have found a case that the Access developers at Microsoft didn't consider.
I might do any of the following things in your case.
- Try to export the VB code to a text file. See if the problem is corrupted VB code. (If so, you will get ANOTHER failure when you do the export.) Try to search the exported text file using the NOTEPAD or WORDPAD editors.
- Do the Find & Replace operation using the "Current Procedure" option on the search. Do it for one procedure at a time until you find the offending procedure. Then you can concentrate on what is wrong with that one part of your code.
- Re-install Office from original media.
- Get the most recent service pack for the operating system. Apply it. It will contain updates for non-OS libraries if they are MS products, so this might help Access at least indirectly.
- Go to the MS web site, search their knowledge base for Find & Replace articles. See if they have similar cases noted.
You, my friend, have found what we call a BUG. {gasp}
Something "impossible" happened to Access that caused a rarely used Windows feature to wake up and take a snapshot of the dying Access application. If you allowed it to do so, this little window you showed us would send a bug report to the folks at Microsoft. They might (or might not) contact you for supplemental information.
You didn't show us the technical information (bottom of the window, one of the two links) so it is hard to know what really happened. But it was probably incomprehensible to anyone who doesn't understand that level of error message anyway.
You might have a bad copy of Access (i.e. need to re-install from CD-ROM) OR you might have found a case that the Access developers at Microsoft didn't consider.
I might do any of the following things in your case.
- Try to export the VB code to a text file. See if the problem is corrupted VB code. (If so, you will get ANOTHER failure when you do the export.) Try to search the exported text file using the NOTEPAD or WORDPAD editors.
- Do the Find & Replace operation using the "Current Procedure" option on the search. Do it for one procedure at a time until you find the offending procedure. Then you can concentrate on what is wrong with that one part of your code.
- Re-install Office from original media.
- Get the most recent service pack for the operating system. Apply it. It will contain updates for non-OS libraries if they are MS products, so this might help Access at least indirectly.
- Go to the MS web site, search their knowledge base for Find & Replace articles. See if they have similar cases noted.
