VBA functions and .net exe's

[SunilChavda]

What’s the comparable speed between a VBA function and .net exe files?

[WorkHorse]

I don't know about .net, but a VB6 exe is going to be a bit faster than VBA because the code is compiled. I would expect VBA functions run at about the same speed as VB6 functions running out of the IDE. Once the code is compiled to an exe it should speed things up.

This is sort of comparing apples to oranges. VB is for making executables, VBA is for customizing existing applications. Most functions in VBA programs will probably be related to the application that the VBA code is for and therefore would depend mostly on the speed of the application. Why would you make an exe that just customizes an app? Why would you use VBA to process code fast or make fancy forms if you can use VB?

Keep in mind also that using VBA to tap the functions built into in Word, Excel, Access, etc. may well be faster (and definitely easier) than any equivalent code you may write in VB.

If you use the right tool for the job, the speed difference should be negligible.

[Eras3r]

when you run a vb6 program from the ide..... it's still being compiled. but its running in the memory space of VB6.exe. Thats why it runs slower than if you were to run your own compiled exe by itself.