A
Arthur Dent
Hello all, Im stumpped.
I have a small app i wrote in VB.NET which takes in a file name, and a bunch
of other params, runs the file with the params, and then exits.
At the end of the program, it can optionally echo back all the params it
received in a msgbox.
When the app is run from a command-line, it works beautifully. The report
runs, then when you close it, the msgbox pops up with the params that were
passed into my launcher program.
HOWever.... we have another application, written in Delphi 4, which attempts
to run the same command line as we tried running manually. When it is run
from the Delphi app, the msgbox with the params never pops up. The Delphi
app is shelling out to my app using the delphi command WinExec().
Is there some weird interaction between Delphi 4 and VB.NET or the .NET
framework in general, that would prevent this msgbox from showing up???
Im truly stumpped, and really need to figure a way to get around this.
Thanks in advance,
- Arthur Dent.
I have a small app i wrote in VB.NET which takes in a file name, and a bunch
of other params, runs the file with the params, and then exits.
At the end of the program, it can optionally echo back all the params it
received in a msgbox.
When the app is run from a command-line, it works beautifully. The report
runs, then when you close it, the msgbox pops up with the params that were
passed into my launcher program.
HOWever.... we have another application, written in Delphi 4, which attempts
to run the same command line as we tried running manually. When it is run
from the Delphi app, the msgbox with the params never pops up. The Delphi
app is shelling out to my app using the delphi command WinExec().
Is there some weird interaction between Delphi 4 and VB.NET or the .NET
framework in general, that would prevent this msgbox from showing up???
Im truly stumpped, and really need to figure a way to get around this.
Thanks in advance,
- Arthur Dent.