- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My Fortran DLL writes a .csv file that users can open in Excel. Sometimes the users may already have an earlier copy open in Excel, so I need to avoid crashing the program if it can't write a file which is already open in another application. The following statement worked fine in Compaq Fortran, but now with Intel Parallel Studio XE 2013, the program crashes if the file is open in another application.
OPEN(16,FILE=csvfile,STATUS='unknown',err=199)
(line 199 initiates a graceful exit from the subroutine)
Any idea why the err=199 doesn't work? Is there another way to accomplish the same thing?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Update: The program is not crashing on the open statement, but on the subsequent Write statement. It appears that there is no error on the open statement, so the Err=199 has no effect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just because you can open a file it does mean you have write access. Put more options on the open (e.g. ACTION='WRITE' or 'READWRITE' or put an error status on the first write....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
app4619: Action='WRITE' works. Thanks for the help.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page