Visual Basic has no built in profiling (speed-tuning data generation type of stuff, that I know of anyway). So I've made some myself but its a bit of a pain but it works (i guess).

For those who don't know profiling your program will generate some results that helps you find the bottlenecks in your code so you can improve the speed.

After the program has run, my profiler will tell me this

for example..

Sub DoThisMan() - Called 8 times, used 35% of program execution time

Sub ProfilingIsCool() - Called 23 times, used 24% of the program execution time

Sub MMmTacos() - Called 43 times, used 5% of program execution time


the list returns the most time consuming routines so I have a place to start looking for optimiziation. My problem is this isn't good enough! I remember profilers back in the day that could profile specific loops of a routine so you could REALLY see the bottlenecks.

Ok gurus lay your ideas on me >

thanks