Dirk Vollmar
2009-02-03 22:24:08
I have seen errors on standard functions if there was a reference to a totally different library missing.
In the VBA editor launch the Compile command from the menu and then check the References dialog to see if there is anything missing and if so try to add these libraries.
In general it seems to be good practice to compile the complete VBA code and then saving the document before distribution.
热门帖子
热门github
6
I agree. Missing references will be clearly marked MISSING. In your case, I suspect it is a later version of the Excel library, which can be got around with late binding, or selecting the earlier library. I do not believe that compiling the code will help with missing references.
Hmm. I'm getting a request for a VBAproject password. The plot thickens.
Time to find the origional developer I think.
I just wanted to add that I too had this problem but in a rather unique scenario. Some machines would have all the DLL's (including in this case Acrobat Distiller) and some would not. I still needed the machines without the Acrobat DLL to run macros that did not use it and so resorted to the VBA. namespace addition for these functions. This resolved the issue and worked in both scenarios.
I just wanted to point that I have meet the same problem, with none of the references marked as MISSING, I haven't found a resolution for it, but a temporary solution is: open the reference dialog in VBE, don't touch anything just click OK, and the VBA project back to normal.