Hi Jim,

I saw a little tip on adding Profiling info to VB code at http://www.planet-source-code.com/xq/ASP/txtCodeId.108/lngWId.1/qx/vb/scripts/ShowCode.htm

The basic idea is to add a uniquie comment to every sub or function in your code (like '*DBG* "Some comment or sub name"). Then do a search and replace on the project with Debug.Print for '*DBG*. You'll have your profiling working, then just switch it back when you're done.

SWAG, AFA getting them in existing code, I believe all the vb code is text right, just drop into VFP or VB and write little progy to add it to all of your VB code. Just look for all the Public Sub, Public Function, etc... and grab the name, then add it to the end of that line.

hth


>I can't just copy and paste Debug.Print "MyMethod" anywhere I want. I would have to actually type in the text for "MyMethod". Definately slows down the process when you just want to see real quick what order things are firing in.
>
>