Hi thank you very much for all your replies and comments...
Its just that I used to make macros without touching or even going t
Visual Basic Editor.
Tool --> Macros --> Visual Basic Editor Alt+F11
I used to combined keyboard shortcuts into one command.
It's like what do we usually do next when we use [Select All o
Ctrl+A]?
We usually use [Copy or Ctrl+C] and the rest.... right?
What if we combine [Select All] and [Copy], and assigned it to
keyboard shorcut or convert it by just "Single click of a button."
Using "Record new macro...." will help...
Tool --> Macros --> Record new macro...
I find these "time saving" on my part... where I usually work as
Document Analyst.... and I used to code 60,000 characters per day wit
99.95-100% quality rating where some of the documents ar
repetitious....
I just want to share this to all of you... it will help you work mor
faster and efficient...
Like what I said "I'm looking for a very useful but not ver
complicated macros"
thank you very muc
--
Message posted from http://www.ExcelForum.com
> Its just that I used to make macros without touching or even going to
> Visual Basic Editor.
Yes, well that's the first part of your problem. If you looked at the code
after creating your macros using the recorder, you'd see just how dreadful a
way this is to create macros: large amounts of redundant code, exclusive
reliance on the Selection object, and wild assumptions about the state of
Word and your document at the time the macro is called.
> I just want to share this to all of you... it will help you work more
> faster and efficient...
On the contrary. Nothing you've suggested here will do that.
> Like what I said "I'm looking for a very useful but not very
> complicated macros"
Using the macro recorder for anything but trivial, quick-and-dirty purposes
gives exactly the opposite -- complicated code that is not very useful.
Malcolm Smith - 05 Nov 2004 10:24 GMT
> Yes, well that's the first part of your problem. If you looked at the
> code
[quoted text clipped - 4 lines]
> of
> Word and your document at the time the macro is called.
Indeed, in fact is there a check that there is a document there at all if
the Selection object is used?
I agree 100% with what you have written here. Using the macro recorder
for production code is not a very good idea at all.
- Malc