- EXCEL FOR MAC 2011 WON'T OPEN IN SAME POSITION EACH TIME HOW TO
- EXCEL FOR MAC 2011 WON'T OPEN IN SAME POSITION EACH TIME CODE
#3 See , Jan Karel Pieterse wrote an UNDO. But if they can’t, store it in a trusted location and users won’t see that warning again.
#4 If it couldn’t be done in native XL and VBA was used, who cares if users freak out. #5 RSadther addressed this – VBA should not use the worksheet’s name but its codename – and then users can rename the sheet whatever they want Hmm… pretty much, if VBA coders learn rule #1, we stop doing all other unnecessary things – including the intent of your list. Lastly, they learn that if native XL can do it, it’s probably best to not use VBA at all.
EXCEL FOR MAC 2011 WON'T OPEN IN SAME POSITION EACH TIME HOW TO
Later they learn how to incorporate native XL functions in VBA (). The normal VBA novice starts out doing everything in VBA. I agree there are times when VBA should not be used so I’ll start with that: You know I love you man but I’m with on this one.
EXCEL FOR MAC 2011 WON'T OPEN IN SAME POSITION EACH TIME CODE
So, it remains to be seen whether the guidance I author entails a tutorial on building my code again (for non VBA users) or simply instructs on the use multiple XL functions in sequence to achieve results.
I am not even part of the IT department, but they have yielded no solutions to the problems faced by the department I am working in. I am reluctant to use a VBA solution, even though I am not rendering it as a “product” or “service” in my employment. Sure, they will save a LOT of time using my solution, but I am not going to be here for long. I am exploring the option of using VBA to streamline a filtering process for administrative duties and the one thing that keeps popping up is the idea that once I have moved on from this short project, the administrators will not have the ability to fix contingent issues or recover the code if it is lost. VBA developers are often completely different from the users that their code will benefit. I agree with you completely from a user point of view. I know this is a very old thread, but Oz, This was a great post. UPDATE (3MAR14) Check out 3 Reasons To Use VBA. (Well … it’s harder to over-do sriracha, but that’s another discussion.)ĭoes anyone else have comments, questions, warnings or stories to share about VBA? My only warning is that VBA is like sriracha: you can over-do it. I set it to run a task that took 48 hours, while I went on with my life and occasionally checked to ensure that the job was still running. Thus, some users can feel like they’ve been abandoned to poke around in a dark alley called The Twilight Zone VBA Editor.Įxcel VBA is splendid. But their Excel wiz may not be familiar with VBA AND have the wherewithal to do the forensics on someone else’s code. Most folks do know an Excel wiz in their life. So, if the VBA-happy developer quits to go chase other dreams in a foreign land, it’s going to be an added challenge for the users to get the document modified or repaired. Many MANY users aren’t aware of VBA or they don’t understand it. Truly, the Numero Uno reason for avoiding (or limiting) use of VBA: If you don’t use good comments in your code, you’ll struggle to understand your own work if you have to revisit it weeks or months later. If the macro is designed to delete information and you run the macro at the wrong time or, the code is wrong and deletes work you spent hours creating … ! You’ll look up and see the UN-DO arrow grayed out. There is no UN-DO! This bears repeating: There is no UN-DO! Some users freak out when they open the workbook and see the security warning about enabling macros. The VBA code has to be manually modified, or you just live with the sheet being called February. VBA does not adjust in the way that formulae do when you move data from one worksheet to another, insert a column, delete rows, etc.Įxample: you have a sheet called February. Sometimes writing, testing and debugging the script will take longer than using worksheet features. There are good reasons to avoid (or at least be cautious about) using VBA. It’s seductive to start thinking in VBA and head straight to the VBA editor with every task. I’ve used VBA to break the passwords on other spreadsheets. The power that’s available is almost frightening. Automating many types of reports and processes for clients.Parsing data in ways that wouldn’t have been possible through worksheet functions.
0 kommentar(er)
