Andre
We had the same problem and solved it by using the 2nd method described by Matthew below - make the VB application test for the existence of an output file before continuing.  It works well.


Abraham Singels
Agronomy Department, Experiment Station
S.A. Sugar Association
Private bag X02,
Mount Edgecombe 4300
South Africa

Tel: 031-5393205         Fax: 031-5395406
[log in to unmask]
www.sugar.org.za/sasex/about/agronomy.htm

>>> [log in to unmask] 04 June 2001 09:38:05 >>>
Andre

I've come across similar timing problems, but with batch files launching
Windows programs. I can't give specific recommendations, but two possible
approaches are:

1) the VB program waits for the DSSAT DOS window to appear, and then close
and then launches the next run. Usually Windows programs can get a list of
the current windows and their titles.

2) the VB program waits for some DSSAT output file to appear (maybe with
size > 0), then renames it and launches the next program.

Sorry I can't be more specific.

Good luck

Matthew Laurenson
Dept. of Information Science and Technology
National Agriculture Research Center
Kannondai 3-1-1
Tsukuba
Ibaraki 305-0035
Japan

ph  +81-298-387025
fax +81-298-388551
e-mail [log in to unmask]
web page http://www.narc.affrc.go.jp/~matthewl/