VBA Good Practice

[gsandy]

I am using the code below at the start and of macros. If I have a macro within a macro should I have this code with just the parent macro or with both parent and child?
If I have a command Button on a form that runs a macro should I use the code below?
Thanks Sandy

Please Login or Register  to view this content.

[mikeTRON]

I generally use those in my code if I want it to run faster and NOT deal with any events (in case you have any event triggers).

[gsandy]

So if I use my code and there is an event trigger the event may not show?

If I have a spreadsheet with a lot of vba coding, and the code only takes a millisecond to run without CodeStart & CodeEnd, and with it half a millisecond (I wont notice the difference) then why have it?

[gsandy]

So if I use my code and there is an event trigger the event may not show?

If I have a spreadsheet with a lot of vba coding, and the code only takes a millisecond to run without CodeStart & CodeEnd, and with it half a millisecond (I wont notice the difference) then why have it?

[AB33]

With events, you need to include them with the event themselves .EnableEvents = False, to avoid the events auto triggering.
I think it is a good coding practice to have separate codes for screening updating and others. Imagine you are writing many small subs and all these subs require these savers. So, instead of repeating these lines in all subs, you put them in a separate codes,so when you need them just call them. This might not save you lots of time but "Do not repeat yourself". is a code modular practice.
Try to insert and copy cells with and with screen updating, you will see the difference.

[gsandy]

Thanks for all the help, Ive got a better idea now. Cheers Sandy.