![]() I recalled having this problem years ago and increasing the pause time between actions fixed it. The first time I ran this macro it simply failed to work with the files not being saved correctly and records being skipped. So that Mac is several orders of magnitude faster than my 2008 model (2Mb RAM, conventional HDD). Fast forward to now, I have a 2019 iMac with 16gb of RAM an SSD, OS Catalina, Office 365 and the latest version of KM.I re constructed this macro in KM and it worked fine on Yosemite OS with Word/Excel 2011and I was able to speed up the macro by reducing the length of the pauses between actions in the macro.I had started the move to KM before this happened. This would make it a global template and give access to macros and keyboard shortcuts in Microsoft Word 2010. With the advent of Catalina, 32bit Applications were no longer supported. I have a macro that needs to be run from the shortcut button. Startly stopped supporting QK some 10 years ago now and as time has gone by the workarounds to keep it running on the latest version of the OS and faster Macs, became ever more tricky.In order to make the macro work I had to insert pauses of around 1.5 seconds into the macro in order that the iMac and screens could keep up. At the time Mailmerge in Word could only produce a single file from a mailmerge operation which was no use as I need to send each document to a different email address 1 What I am trying to create is a writing assistant for MS word that gives me advice during writing. I first used this macro in Quickeys way back in 2009 on a 2008 iMac, using Word & Excel of that time.īasically the macro copies and pastes entries from 2 adjacent cells in an Excel spreadsheet into a word document which is then saved as a file using the data from one of the spreadsheet cells as the file name.Here are a couple of marginally interesting things By default, access to a Word VBA project is disabled. Additional notes for Word 2002 and Word 2003. When you click the CommandButton control, the Click event of the control fires. Select Macros From View Tab From the drop-down list, select View Macros. Interestingly running the macro in the debug mode never failed until I swapped from stepping through it to running it. Once the macro 'Test' finishes running, you will see a new CommandButton control on a new document. From the View tab of the Ribbon, in the Macros group, select Macros. Thank you for your help, I have gone with your idea of calling the macro, Chris's solution worked as well, it helped me a bit as your solution separated the Repeat from the actual macro and helped to trouble shoot it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |