- ©«¤l
- 3
- ¥DÃD
- 1
- ºëµØ
- 0
- ¿n¤À
- 5
- ÂI¦W
- 0
- §@·~¨t²Î
- WIN7
- ³nÅ骩¥»
- OFFICE2010
- ¾\ŪÅv
- 10
- µù¥U®É¶¡
- 2014-11-24
- ³Ì«áµn¿ý
- 2020-11-16
|
¦^´_ 3# clietj37
¤j¤j§A¦n¡Aè¤~¤w¸g¬Ý¹L§Aªº´£¨Ñªº¸Ñ¨M¤è¦¡¡C¦]¬°¦³¨Ç¹q¸£¤´µM¤£¦¨¥\¡C©Ò¥H§Ú°Ñ¦Ò¤å³¹¤¤ªºAdditional Step
Additional step:
If the steps above do not resolve your issue, another step that can be tested (see warning below):
On a fully updated machine and after removing the .exd files, open the file in Excel with edit permissions.
Open Visual Basic for Applications > modify the project by adding a comment or edit of some kind to any code module > Debug > Compile VBAProject.
Save and reopen the file. Test for resolution. If resolved, provide this updated project to additional users.
Warning: If this step resolves your issue, be aware that after deploying this updated project to the other users, these users will also need to have the updates applied on their systems and .exd files removed as well.
¬Ý±o¤£¬O«ÜÀ´"modify the project by adding a comment or edit of some kind to any code module > Debug > Compile VBAProject."¬On°µ¤°»ò? ¬OÀH«K½s¿èVBA¤¤¥ô¦ó¤º®e¶Ü? Debug ¸ò Compile VBAProject ¨CÓ¦r³£ª¾¹D·N«ä¡A¦ý¥[°_¨Ó´N¤£ª¾¹D¹ê»Ún¶i¦æ¤°»ò°Ê§@...?{:3_60:}
¦ý§ÚÀH«K½s¿è¤@¤U«á«¶}ÀÉ®×´N¥X²{§Ú¦b#4´yzªº±¡ªp¡C¨D¤j¯«¸Ñ´b~~ |
|