I'm using a simulation software (GenOpt) to run some building energy simulations, and I have written a custom .exe using visual basic to do some data processing for me. In a preliminary version of the VB script, it read one file and output one value to a text file. When I use this version (version A), GenOpt executes properly. When I use a more recent VB script version (version B, which has the rest of the data processing I actually need), the simulation program hangs up - like it's waiting for the process to finish, not realizing that it actually has. The only difference between the two is which .exe I use.
This makes me think there must be something different about how I'm handling system processing in version B. Unfortunately, I don't know what GenOpt is looking for while it's waiting for the process to complete.
Can anyone point me in the direction of things to try or look for in my code that can tell the calling program that the process has completed?