get value from an external application that was opened via shell command

I'd like the user to be able to click a button on my access form and open an
external application (built in .net 1.1). This application needs to behave
like a modal dialog within access. The user will do what he needs to in
this application and then close it. At that point, the remaining VBA code
after the shell command should resume.

How can I accomplish this kind of 'modal' behavior with an external
application. Is it possible through managed VBA code or APIs?

Thanks!

Do you really mean modal (i.e. the application must remain on top of
everything else), or is asynchronous enough (i.e. VBA doesn't continue
executing until the application is shut down)?

If the latter, check http://www.mvps.org/access/api/api0004.htm at "The
Access Web".

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jesse Aufiero" wrote in message
...
I'd like the user to be able to click a button on my access form and open
an external application (built in .net 1.1). This application needs to
behave like a modal dialog within access. The user will do what he needs
to in this application and then close it. At that point, the remaining
VBA code after the shell command should resume.

How can I accomplish this kind of 'modal' behavior with an external
application. Is it possible through managed VBA code or APIs?

Thanks!

Doug,

That is what i'm after. Thank you!

"Douglas J. Steele" wrote in message
...
Do you really mean modal (i.e. the application must remain on top of
everything else), or is asynchronous enough (i.e. VBA doesn't continue
executing until the application is shut down)?

If the latter, check http://www.mvps.org/access/api/api0004.htm at "The
Access Web".

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jesse Aufiero" wrote in message
...
I'd like the user to be able to click a button on my access form and open
an external application (built in .net 1.1). This application needs to
behave like a modal dialog within access. The user will do what he needs
to in this application and then close it. At that point, the remaining
VBA code after the shell command should resume.

How can I accomplish this kind of 'modal' behavior with an external
application. Is it possible through managed VBA code or APIs?

Thanks!

Well, I think I spoke too soon. This 'shellwait' method is buggy at best.
If i click the access application more than 4 times, it shifts access into
'not responding' mode. Also, access does not repaint for the duration of
the shellwait, so if the user moves the shelled app, resizes it, or drops
down a comobox dropdown beyond the borders of the shelled app's form
borders, access does not repaint itself, leaving a visual garbled mess under
the shelled application.

Is there a shellWait that works better? Or an all together different
strategy to force access to 'wait' for a shelled app to close before
resuming vba code?

Thanks!


"Jesse Aufiero" wrote in message
...
Doug,

That is what i'm after. Thank you!

"Douglas J. Steele" wrote in message
...
Do you really mean modal (i.e. the application must remain on top of
everything else), or is asynchronous enough (i.e. VBA doesn't continue
executing until the application is shut down)?

If the latter, check http://www.mvps.org/access/api/api0004.htm at "The
Access Web".

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jesse Aufiero" wrote in message
...
I'd like the user to be able to click a button on my access form and
open an external application (built in .net 1.1). This application
needs to behave like a modal dialog within access. The user will do
what he needs to in this application and then close it. At that point,
the remaining VBA code after the shell command should resume.

How can I accomplish this kind of 'modal' behavior with an external
application. Is it possible through managed VBA code or APIs?

Thanks!

See whether you're any happier with what Randy Birch has at
http://vbnet.mvps.org/code/faq/getexitcprocess.htm

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Jesse Aufiero" wrote in message
...
Well, I think I spoke too soon. This 'shellwait' method is buggy at best.
If i click the access application more than 4 times, it shifts access into
'not responding' mode. Also, access does not repaint for the duration of
the shellwait, so if the user moves the shelled app, resizes it, or drops
down a comobox dropdown beyond the borders of the shelled app's form
borders, access does not repaint itself, leaving a visual garbled mess
under the shelled application.

Is there a shellWait that works better? Or an all together different
strategy to force access to 'wait' for a shelled app to close before
resuming vba code?

Thanks!


"Jesse Aufiero" wrote in message
...
Doug,

That is what i'm after. Thank you!

"Douglas J. Steele" wrote in message
...
Do you really mean modal (i.e. the application must remain on top of
everything else), or is asynchronous enough (i.e. VBA doesn't continue
executing until the application is shut down)?

If the latter, check http://www.mvps.org/access/api/api0004.htm at "The
Access Web".

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jesse Aufiero" wrote in message
...
I'd like the user to be able to click a button on my access form and
open an external application (built in .net 1.1). This application
needs to behave like a modal dialog within access. The user will do
what he needs to in this application and then close it. At that point,
the remaining VBA code after the shell command should resume.

How can I accomplish this kind of 'modal' behavior with an external
application. Is it possible through managed VBA code or APIs?

Thanks!