![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Banana <Banana (AT) Republic (DOT) com> wrote in news:4BCA348B.4070507 (AT) Republic (DOT) com: Now with 2010, I can see some use in using macros for simple tasks and for data macros & web databases (where there's no choice anyway) and I'm quite glad they enhanced the macro language - it's not full bodied as VBA and I will continue to write more VBA than macros but it's improvement nonetheless. My concern with macros, even in their new guise, is managing them. In VBA you can easily tell what's in use and what's not, because it's compiled. That is, you can rename a function/sub, hit the compile button and immediately know if it's redundant code that can be removed. With macros, you can't do that. Secondly, unless I haven't heard about it, there's no way to browse through and search all macros and see what's interconnected. Embedded macros were introduced in A2007 and they make it even harder, in my opinion, to tell where things are happening. So, troubleshooting seems to me like it would be very difficult. Also, the main way I make my living is taking over old apps that need revival, and very often this means figuring out a tangle of spaghetti macros and rationalizing it into something more manageable. If there has been no improvement in the tools for maintaining and auditing macros, I, too, will avoid them for anything where they are not essential (just like I do already). -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
![]() |
| Thread Tools | |
| Display Modes | |
| |