d_l Posted December 23, 2007 Share Posted December 23, 2007 I don't have Excel and can't view the log. Lotus 123 (yes, there are some people that use this) chokes on the ISY XLS output. Wordpad sees the XLS code and shows nothing intelligible. Not having seen what the Excel presentation actually looks like, I'm at a loss as to why you would need to use a spreadsheet to list a log file. Is this to format the output in columns and rows or to produce a three-dimensional layered organization? Link to comment
Mark Sanctuary Posted December 23, 2007 Share Posted December 23, 2007 The xml file shows nicely in Word. There is also the "Getting a Network Typology Table" you can use to get a html table version of your network. Link to comment
jgraziano Posted December 23, 2007 Share Posted December 23, 2007 I can't view it in Excel either because the version on my home machine is too old (2000). There are macros in there to be able to sort the entries via drop-down, but my version chokes on them. My work laptop has 2003, works fine. It does show up also, when you generate the log, as an .rtf Word file. In my case, it is at the following path: C:\Documents and Settings\Owner\Local Settings\Temp\UDReport.rtf Not much on formatting, but the information is there. Link to comment
Mark Sanctuary Posted December 23, 2007 Share Posted December 23, 2007 I added the xml Excel viewing instructions to the same Wiki page. Link to comment
d_l Posted December 23, 2007 Author Share Posted December 23, 2007 So if I understand this correctly, the XML entries of the log are sent to Excel in a recent Excel format by having an XLS extension on the output. This all came up because I suddenly wondered if I had any errors in the log file and that I may have been flying blind with respect to that possibility. Mark, thanks for the Word suggestion, but how would someone get the XLS output to Word. By changing the program associated with the XLS extension? I don't have Word either (I have WordPerfect because I'm really old school) so it doesn't help me, but might help someone else. Jim, thanks for the location of that rtf file. At least, I found it and could read it with WordPad. I see the log file only logs Insteon activity. I've over a month of activity to review and check the error codes. Dave Link to comment
Michel Kohanim Posted December 23, 2007 Share Posted December 23, 2007 d_l, I am so very sorry for the problems and issues. If you do not have Excel (and are running Windows), currently the only way to get to your logs is as jgraziano suggested. On MAC/Linux, you are given the log file as is. We do have a requirement to provide this function without Excel on Windows so, please do be kind enough to use jgraziano's suggestion as a workaround. With kind regards, So if I understand this correctly, the XML entries of the log are sent to Excel in a recent Excel format by having an XLS extension on the output. This all came up because I suddenly wondered if I had any errors in the log file and that I may have been flying blind with respect to that possibility. Mark, thanks for the Word suggestion, but how would someone get the XLS output to Word. By changing the program associated with the XLS extension? I don't have Word either (I have WordPerfect because I'm really old school) so it doesn't help me, but might help someone else. Jim, thanks for the location of that rtf file. At least, I found it and could read it with WordPad. I see the log file only logs Insteon activity. I've over a month of activity to review and check the error codes. Dave Link to comment
MikeB Posted December 23, 2007 Share Posted December 23, 2007 How about the free Excel viewer: http://www.microsoft.com/downloads/deta ... laylang=EN Link to comment
Mark Sanctuary Posted December 23, 2007 Share Posted December 23, 2007 The trick here is Excel has to have the XLM filter to bring XML into Excel. Excel by its self would not view it without the built in filter which I think is "being" installed with the default install of the Office disk. So if the free viewer has the built in filter with it will work. Link to comment
Michel Kohanim Posted December 23, 2007 Share Posted December 23, 2007 Mark, We do not use XML in the logs. With kind regards, The trick here is Excel has to have the XLM filter to bring XML into Excel. Excel by its self would not view it without the built in filter which I think is "being" installed with the default install of the Office disk. So if the free viewer has the built in filter with it will work. Link to comment
Mark Sanctuary Posted December 23, 2007 Share Posted December 23, 2007 Oops my mistake. I don't think I have looked at the logs yet. Link to comment
Mark Sanctuary Posted December 23, 2007 Share Posted December 23, 2007 Michel, Could you make the logs CSV (comma separated values)? Then any spreadsheet program could open it. Link to comment
Michel Kohanim Posted December 23, 2007 Share Posted December 23, 2007 Mark, They are already Tab Delimited. With kind regards, Michel Michel, Could you make the logs CSV? Then any spreadsheet program could open it. Link to comment
d_l Posted December 23, 2007 Author Share Posted December 23, 2007 We do have a requirement to provide this function without Excel on Windows so, please do be kind enough to use jgraziano's suggestion as a workaround. Michel, thanks. It hasn't been that much of a problem. I'm all set now with a WordPad shortcut to UDReport.rtf as per jgraziano so all is golden. Link to comment
jgraziano Posted December 23, 2007 Share Posted December 23, 2007 They are already Tab Delimited. If you open it with Excel as a tab-delimited file, it displays very nicely. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.