To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=41695
------- Additional comments from [EMAIL PROTECTED] Wed Aug 31 12:27:22 -0700 2005 ------- Perhaps I have missed something in the bug reports, but I am using OO 2.0-pre (build 1.9.110 installed with SuSe 9.3 Pro), and this bug is still present. The get statement produces a syntax error (using it with a binary file, haven't tested with random). Also, when I switch back to the oocalc window, the syntax error keeps popping up in both the oocalc and basic windows repeatedly, so fast that the only way to regain control is to kill soffice. Related: the "line input" command fails to return an error when it encounters binary (non-text) data. Instead, when running in an oocalc macro, the basic window will open with the "line input" command highlighted, but with no error displayed. This is even the case when it is within an error trap. The error is not trapped. For example, consider if the "test.htm" file is corrupt and incorrectly begins with these bytes: 0x1F 8B 08 00 00 on error goto errx open "test.htm" for input as 1 'same result if opened as binary line input #1, a close 1 In my thinking it should return an I/O error (which would be trapped). As it stands, there is no way to trap it and the macro stops. With the get command missing, there is also no way to read the file and verify it is a text file. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]