Quote:
Originally Posted by equalizer88
With similar program written in "C", I'm sure overhead is much lower
|
That doesn't necessarily follow. VBA isn't like its ancient predecessor, GW-Basic. Before execution, even VBA is semi-compiled, so all you might save is the compilation time. Besides, which would you prefer - a process that runs as quickly as possible, thereby hitting as much as 90% CPU usage, or one that keeps the CPU usage down to 25% but takes four times as long to complete (not that I'm suggesting C#-code would do this)?
08-16-2015, 04:56 PM
Similar Threads
VBA Batch Find & Replace for all MSOffice extensions, to replace File Name and Content of the File
Windows 7 64bit 
Office 2010 32bit
Threaded Mode