I did not examine that excel file in the link I posted, but I expect that you should need to make adjustments for it to work in your particular situation.
If you open the Help file in RSLinx and search for "Excel OPC" there should be some advice for how to set up an OPC topic pointed at your PLC.
The cause of the error and the details of how to record the data may require picking apart the VBA code in the excel workbook. (I assume there is some code behind the scenes that attempts to open RSLinx and set up the topic.) I do not have Excel here at home, and Open Office Calc does not use VBA so I did not bother to try and check it out for myself.
I have done something similar in the past, but in my case I did not have quite enough error handling to make it ready for publishing. I also found that even when everything was perfect, RSLinx or Excel would hang at least once per week. I was only doing the "cheap and dirty" logging as a trial to see what I could learn and also to save operations management from having to go around with a notepad to all the machines and write down numbers. When it worked it was a time saver for them, but it was not worth any more of my time to make it more reliable.
If you want something you can count on day in and day out and it needs to become part of your operation that you rely on, then go with a higher end solution.
You version of RSLinx does support DDE/OPC, so what you are trying to accomplish is feasible and if you hash out all the details and possible errors, it might be worth the effort depending on how valuable your time is.