VBA Needed - Report which VBA code already run which not in same

[Myproblem]

hello VBA funs,

I have many VBA codes in the same workbook - monthly report (dont ask why), and in the same workbook and in the couple hours of working in it I do not know which VBA I already run, which not.
I need VBA which will show, in separate sheet (in the same workbook) or in the new workbook which VBA codes alredy run regarding same workbook and which not.

thx
any tips

 

[VBACO]

I think this would solve your problem.

http://www.exceltip.com/st/Log_files_using_VBA_in_Microsoft_Excel/493.html

 

[Myproblem]

I think this would solve your problem.

http://www.exceltip.com/st/Log_files_using_VBA_in_Microsoft_Excel/493.html

thx for link but i think it is not what i looking for, the links are all about workbook login information, i need information about when and which vba run and which not run in the same workbook

 

[tweedle]

I think he's trying to point you to methods of how to log the vba runs, which is applicable to your inquiry.
You would need to call the logging mechanism from each module/function to create the log - which could ultimately show you what was run on which file when and by whome.
There is no native tracing of this in VBA to back-track what has already been run.

 

[Myproblem]

I think he's trying to point you to methods of how to log the vba runs, which is applicable to your inquiry.
You would need to call the logging mechanism from each module/function to create the log - which could ultimately show you what was run on which file when and by whome.
There is no native tracing of this in VBA to back-track what has already been run.

After searching for adequate properties i figure out almost the same - there is no simpe, unique tracing about VBA already been run.

Maybe i am wrong, or i figure out wrong but there is no propertie for VBA code? Am I wrong?

But i still do not know any example if VBA code to call logging mechanism for each module, or subroutine in specific (only one) workbook

any idea

 

[tweedle]

Maybe i am wrong, or i figure out wrong but there is no propertie for VBA code? Am I wrong?

There are - one would need to add a reference to "Microsoft Visual Basic for Applications for Extensibility" from Tools/References to access the properties (.LastRun is not one of them).

 

[Myproblem]

There are - one would need to add a reference to "Microsoft Visual Basic for Applications for Extensibility" from Tools/References to access the properties (.LastRun is not one of them).

In Excel 2007 I have "Microsoft Visual Basic for Applications for Extensibility 5.3", it should be that, isnt it?

 

[tweedle]

Yes, that's the reference.
I'm not fluent in the object; but believe hat this is primarily used for add-ins relative to manipulatine the VBA Code in IDE. It's a little deeper than just running a logger and, imho, has good potential for really hosing one's project.

 

[Myproblem]

i figure out how to solve this problem,
i will put name of the vba code before end sub, and make stamp time and date on new worksheet.

thx tweedle

 

[tweedle]

Yes, that's the idea;
whether using the logger pointed to by VBACO or some other function.

You would need to call the logging mechanism from each module/function to create the log - which could ultimately show you what was run on which file when and by whome.