C++ / Visual Basic question - Tilted Forum Project Discussion Community

dimbulb · 09-02-2003, 09:10 AM

So i have a executable written in C++, and i wish to call this executable in Visual Basic, and be able to read results from running the C++ program.

The C program outputs its results in a text file when it's done running.

So my question is, how do I check, from Visual Basic for Applications, that the C program is done running?

thanks.

SaltPork · 09-02-2003, 10:07 AM

You have to use ShellandWait I think from advapi32.dll.

Flippy · 09-02-2003, 04:36 PM

I would use Shell, get the process ID, and use OpenProcess with the SYNCHRONIZE flag set.

Then, with the handle obtained from OpenProcess, use WaitForSingleObject

cowlick · 09-02-2003, 08:21 PM

So am I out of line in suggesting you simply throw a COM interface on the C++ program and load it from VB to get a rich programatic exchange?

GreasyP · 09-10-2003, 08:51 PM

Quote:

Originally posted by cowlick
So am I out of line in suggesting you simply throw a COM interface on the C++ program and load it from VB to get a rich programatic exchange?

Not at all, though some might argue the word "simply" is a bit misleading...

Syncronizing the processes like ^^^ they said up there is probably easiest.

cowlick · 09-12-2003, 09:37 AM

Crud. I find VB one of the most annoying languages ever. What a lax grammar they build that language on.
I'd much rather C, C++, C#, Java, Lisp, JScript, Fortran...

09-02-2003, 09:10 AM	#1 (permalink)
dimbulb Riiiiight........	C++ / Visual Basic question So i have a executable written in C++, and i wish to call this executable in Visual Basic, and be able to read results from running the C++ program. The C program outputs its results in a text file when it's done running. So my question is, how do I check, from Visual Basic for Applications, that the C program is done running? thanks.

09-02-2003, 10:07 AM	#2 (permalink)
SaltPork Everything's better with bacon Location: In your local grocer's freezer.	You have to use ShellandWait I think from advapi32.dll. __________________ It was like that when I got here....I swear.

09-02-2003, 08:21 PM	#4 (permalink)
cowlick Insane Location: Seattle	So am I out of line in suggesting you simply throw a COM interface on the C++ program and load it from VB to get a rich programatic exchange? __________________ "It's a long story," says I, and let him up.

09-12-2003, 09:37 AM	#6 (permalink)
cowlick Insane Location: Seattle	Crud. I find VB one of the most annoying languages ever. What a lax grammar they build that language on. I'd much rather C, C++, C#, Java, Lisp, JScript, Fortran... __________________ "It's a long story," says I, and let him up.

09-02-2003, 04:36 PM	#3 (permalink)
Flippy Banned Location: Greater Vancouver	I would use Shell, get the process ID, and use OpenProcess with the SYNCHRONIZE flag set. Then, with the handle obtained from OpenProcess, use WaitForSingleObject