|
Something very non-fun has happened to my installation of Access 2000. I was in the middle of creating a database that I need to install up at PTC in Rhode Island, when it suddenly crapped out. Everytime I triggered an event on a form, I got a "Module not found" error. I tried repeatedly to point Access to the proper modules, but it wasn't having any of that. So I then tried to reinstall and got caught in the "slacker cycle of doom". Right after I started the reinstall process, I went on the web to surf around to kill time until the installation was completed. After every visit to one of my usual quickie websites, I would flip back to see the progress. And that little status bar was just dra-a-a-agging its way across the screen. Finally I had had enough and closed explorer. As soon it closed, the status bar zipped the rest of the way across the screen and finished up. It was Windows Explorer that was hanging me up in the first place! Bastards!
It turns out that two forms that I had created had their Visual Basic modules cross saved or something. I exported all the code to a blank database and was able to recover everything except those two forms. So I recreated the forms and cut-and-pasted their code from the corrupted database. It seems to be working. That will teach me to not to keep my code on the server to get backed up.
|
