Question using Open Statement on Server

[Michael8]

Hello:

I have created the following simple test program:

program Test  open(10, name='temp1', status='old', err=1)  stop1 open(10, name='temp1', status='replace')
end

It works fine (i.e. it doesn't crash) when I run it from my local machine. But when I copy the solution and project to a server directory (to which I havefull write permission), and run it from the server, it crashes at line 1 saying that it can't open the file. I noticed, though, that if I change the file names to "D: emp1" (so that it's trying to open the file on my local machine), then it runs, even from the server.

This seems strange to me. What am I missing? Is it perhaps a compiler bug?

Thanks.
Michael

[Michael8]

I had my hopes up that this would finally help you replicate my crash. Oh well.

I can open a command prompt, change into the mapped drive, and thenrun the program. I get the same result as before. But I'm not sure if I understand what you mean to "set the default to the mapped drive".

Also, I think there must be some other inherent difference in our systems. I can't understand why you're getting that message about the UNC drive. I've gotten that message before for other programs that I've tried to run over the netweork, but only if I do something like calling the "system" (or "systemqq") function. This sample program is simply trying to open a file using the standard Fortran "open" statement. That shouldn't cause the UNC error (or rather, warning) message, as far as I understand.

Thanks.
Michael

[Steven_L_Intel1]

What I meant was: Map the share as a drive letter, say, Z:. Open a command prompt window and type:

Z:

Now CD to the folder with the EXE and run it.

I see the UNC error as soon as I try to run the program from within VS, since VS tries to set the current directory to the project directory.

[Michael8]

OK, thanks for the clarification. I've done that already and it did not make any difference. See my attachment in the fifth post of this thread (my 3rd post), called ErrorMsg2.jpg.

I don't that message from VS. Which leads me to guess that we're running different version of VS. I'm using Visual Studio .NET 2003. I guess you're probably using a more updated version, Visual Studio2005?

Is there any way you could try this experiment using .NET 2003. I'm going to see if we have a VS 2005 around here that I can play with.

Thanks.
Michael

[Michael8]

Another thing to try, Steve: What happens if you just double click on the executable that's on your server (i.e., without starting it through Visual Studio, and without using a mapped drive)? Do you still get the UNC warning message? You may need to put a "pause" statment in the program so you can see if you get the message before the window closes.

Thanks.
Michael

[Steven_L_Intel1]

I did try this with VS03. Had been using VS08 earlier.

Double click EXE in window with UNC path - works, no message
Open solution with UNC path and run from within VS - works, no message

Here's all of what I did.

1. On W2003 Server, copied my solution folder to the local drive
2. Specified that the local folder should be shared
3. Added permission that gave me full access
4. On my desktop, opened an Explorer window and typed in the UNC path
5. Double clicked EXE or SLN (to try running from VS)

[Michael8]

Once again, thanks for all your efforts.

Even though the actual code where this issue originally cropped up is a lot more convoluted than the simple program I posted, I'm going to have to try and untangle it to avoid these types of "openings" of files.

Thanks.
Michael