I've been working on an Access 2000 VBA project.
Time and again I've opened my project only to find that the VBE is all hosed up.
The first time it happened I was more than a little annoyed. I followed the instructions in MS KB article 248960 for recovering a corrupted project.
The recovery procedure (modified from the article):
1) create a blank database
2) export ALL Access objects to this database
3) re-establish relationships
4) re-establish any broken references
(No system tables are exported.)
I've had to recover my project MANY, MANY times!
The DAO 3.6 and Word 9.0 library references are consistently broken. (I'm doing some Word automation in my project.)
I can't for the life of me figure out what is causing this.
Has anyone else encountered this?
Craig Meyers, BSNucE, PE
Time and again I've opened my project only to find that the VBE is all hosed up.
The first time it happened I was more than a little annoyed. I followed the instructions in MS KB article 248960 for recovering a corrupted project.
The recovery procedure (modified from the article):
1) create a blank database
2) export ALL Access objects to this database
3) re-establish relationships
4) re-establish any broken references
(No system tables are exported.)
I've had to recover my project MANY, MANY times!
The DAO 3.6 and Word 9.0 library references are consistently broken. (I'm doing some Word automation in my project.)
I can't for the life of me figure out what is causing this.
Has anyone else encountered this?
Craig Meyers, BSNucE, PE