Mitsules, Mark S. (Newport News)
Mark.Mitsules at ngc.com
Thu May 6 09:34:52 CDT 2004
The different versions of ShellWait utilize the API call CreateProcessA instead of ShellExecuteA. I can't seem to get CreateProcessA to open anything...yet no errors are returned. Is CreateProcessA like ShellExecuteA in that as long as I pass a valid path/filename with a registered extension, it will automagically do its thing? ...because it isn't:( Mark -----Original Message----- From: Mitsules, Mark Sent: Thursday, May 06, 2004 9:41 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] ShellExecute / Application.Quit Thank you. I'll test it out. Mark -----Original Message----- From: Gustav Brock [mailto:gustav at cactus.dk] Sent: Thursday, May 06, 2004 9:02 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] ShellExecute / Application.Quit Hi Mark Look up "A2K: Shell 'discoveries'" from 2004-04-22 in the archives for an example. /gustav > The following code snippet works if stepped through manually. It also works > when attached to a macro that is manually run. It does NOT work when run in > an AutoExec macro. I'm guessing that it is a timing issue...is it? Any > suggestions? > If fShellExecute(strAction, _ > strFileName, constInstallPath) Then > Application.Quit > End If -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com