Fortran executable with Visual Basic : delay was due to parallel processing


aka wrote:
thank you guys...

problem is solved but i am still lokking for a better way !!!

everything was fine... the only problem was the executable was being
called as a parallel process.. and the compiler was reaching the
section of the VB code that uses the output file even before its
generation was complete from the fortran executable and giving an error
of file not found

the output file was being generated but with a delay.

So I now keep a dummy blank txt file with the same name in the
directory. Which is later on over written by the file generated from
fortran.... and it works !!!

Though I am still looking for a better way....

Any suggestions

glen herrmannsfeldt wrote:
akansha.khandelwal@xxxxxxxxx wrote:
(snip)

I do this using shell command. The shell command returns a number
(probably task sequence) which proves that the fortran exe is executed
but output file is not generated.

It will be in the current directory of the program that created
it, which may not be where you expect.

-- glen

.