Tracking changes in excel file (excel 2000/2003)

Topic

New Reply

Hello,

I am trying to see if there is a way we can track changes in excel file either via VB or any other way. I was also wondering if anyone knows how I can go about stepping into a macro to watch each line of VB(macro) is doing. I would like to see both the worksheet and the VB in the screen as is stepping into it. Thanks.

Reply | Quote

Replies

1) See Tools | Track Changes…

2) You can arrange the Excel and Visual Basic Editor (VBE) windows side by side, or maximize Excel and place the VBE window so that it leaves the relevant part of the worksheet visible.
Click in a macro, then press F8 to single-step through the code. You can inspect the value of variables, properties etc. by hovering the mouse pointer over them in the code.
You can resume automatic execution by pressing F5.
You can also set a breakpoint on a line by clicking in the grey margin to the left of it, or by clicking in the line and pressing F9. (Repeating this toggles the breakpoint off)
When you run the macro, execution pauses at the breakpoint, you can then use F8 to single-step.

Reply | Quote

Thanks Hans. Do you know if there is a way to get a history for an excel file of a user making changes. For example, I want find out the last person that made changes to a file and date.

Reply | Quote

Again: See Tools | Track Changes…

There is an option to display a history of changes in a separate worksheet. This option will only become available after the workbook has been saved as a shared workbook.

By the way, sharing workbooks is a possible source of workbook corruption. Unless you absolutely need this, I would recommend NOT sharing a workbook (and hence, not being able to track changes)

Reply | Quote

[indent]

---

“By the way, sharing workbooks is a possible source of workbook corruption.”

---

[/indent]
It also leads to unbelievable file bloat and slows excel down like nothing you have ever seen before (at least on our system) – tried it once; won’t make that mistake again….

Reply | Quote