I ran this example two ways, one using the Open command to read the table from another file (Table example 2.OUT), the other using the Table command to read the table within the program (Table example 1.OUT). Both worked, and the results were identical to each other, and to the example in the ODA book.
I use command prompt to run ODA software, as I find it much more efficient than using PFE. However, Rob uses PFE, and we tested all the examples using -- all methods and various computers.
Thus, I suspect a misspelling may be the problem. The program creates a file called ODA.OUT that lists any programming issues.
PS: The attachment you provide is too small for me to see, I was unable to make Windows expand the font size, and some of the information is truncated at the right-hand side. It looks as though, in the second line, the extension may be "cnd"? Perhaps it should be "cmd"?
The program works for me, so again, I suspect that either the file name is misspelled somewhere--the data file can't be found. Please post what you find. I am leaving soon for about two hours...
PS-2: Doh on me, I was able to expand the font size, and it looks like an "m", not an "n" to me. If you can't find the spello, I recommend trying it using the Table command (Table example 1.OUT), to verify that the system *is* working, and then you'll know for certain that there is a spelling issue, or the file isn't where its supposed to be. Outta here for now...
On my little hike I just saw a high-end Ferrari stopped at a red. I saluted, of course, and the driver smiled and launched the machine off of the green light to give me a little thrill. With command prompt, and using all four partitions of my quad core to parallel process, ODA software runs similarly...