Technically, can anyone explain to me why Cells.Find() is so much faster than a loop?
 

Can someone please explain to me why it is so much faster to use the
built in application functions, particularly for searching, when
programming an Excel Macro than creating a loop? Thanks for your time.

Technically, can anyone explain to me why Cells.Find() is so much
 

Built in functions are compiled executables where as VBA is not. Additionally
VB/VBA is not the most efficient language when executed where are as the
built in functions are probably using C/C++ or something similar.
--
HTH...

Jim Thomlinson


"Will" wrote:

Can someone please explain to me why it is so much faster to use the
built in application functions, particularly for searching, when
programming an Excel Macro than creating a loop? Thanks for your time.

Technically, can anyone explain to me why Cells.Find() is so much
 

On Nov 6, 1:39 pm, Jim Thomlinson <James_Thomlin...@owfg-Re-Move-
This-.com wrote:
Built in functions are compiled executables where as VBA is not. Additionally
VB/VBA is not the most efficient language when executed where are as the
built in functions are probably using C/C++ or something similar.
--
HTH...

Jim Thomlinson

"Will" wrote:
Can someone please explain to me why it is so much faster to use the
built in application functions, particularly for searching, when
programming an Excel Macro than creating a loop? Thanks for

I'm not very versed in computer programming, but how are compiled
executables in dealing with system resources? What about a compiled
executable makes it faster other than running through a VBA compiler
like a hand-made macro?

Technically, can anyone explain to me why Cells.Find() is so muchfaster than a loop?
 

Check your other post.

Will wrote:

Can someone please explain to me why it is so much faster to use the
built in application functions, particularly for searching, when
programming an Excel Macro than creating a loop? Thanks for your time.

--

Dave Peterson