BUG: An OPEN Status= Option Like String Converted to Uppercase

Last reviewed: April 9, 1996
Article ID: Q149513
The information in this article applies to:
  • Microsoft Fortran PowerStation for Windows 95 and Windows NT, version 4.0

SYMPTOMS

Compiling a source file that contains a character string that is the same as an OPEN statement status= option (that is: new, old, scratch, unknown) is inadvertenly converted to uppercase. This problem occurs when an OPEN statement is in the same source file and uses the same status= character string.

RESOLUTION

Assign the status= option string to a temporary variable, and then use the temporary variable as the OPEN statement's status= option.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Compiling the following source code causes the print statement's 'unknown' string to be converted to uppercase. Note the OPEN statement must be in the same source file and has to use the same status= string for this to occur.

Sample Code

! Compile options needed: none

! uncomment the following line for work-around ! character*7 :: openstatus = 'unknown'

      print *, 'the following should be lowercase: ', 'unknown'
! comment the following line for work-around
      open(unit=20, file='test.out', status='unknown')
! uncomment the following line for work-around ! open(unit=20, file='test.out', status=openstatus)
      end

Output

the following should be lowercase: UNKNOWN


Additional reference words: 4.00
KBCategory: kbprg kbbuglist
KBSubcategory: FORTLngIss



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.