I'm thinking the fault might be the application. The application is
called with a command file that tells the application to run minimized
- could that in any way conflict with the WaitForSingleObject code?
The code that is called in the function is:
ShellPause "c:\iq\iqobject\iqpersnl.exe @g:\common\xray\XXX.cmd"
(where xxx is replaced by the network login name through another API
call)
Here's the slightly modded ShellPause code:
Option Compare Database
Option Explicit
'***************** Code Start ******************
'This code was originally written by Terry Kreft.
'It is not to be altered or distributed, 'except as part of an
application.
'You are free to use it in any application,
'provided the copyright notice is left unchanged.''Code Courtesy
of'Terry Kreft
Private Const STARTF_USESHOWWINDOW& = &H1
Private Const NORMAL_PRIORITY_CLASS = &H20&
Private Const INFINITE = -1&
Private Type STARTUPINFO
cb As Long
lpReserved As String
lpDesktop As String
lpTitle As String
dwX As Long
dwY As Long
dwXSize As Long
dwYSize As Long
dwXCountChars As Long
dwYCountChars As Long
dwFillAttribute As Long
dwFlags As Long
wShowWindow As Integer
cbReserved2 As Integer
lpReserved2 As Long
hStdInput As Long
hStdOutput As Long
hStdError As Long
End Type
Private Type PROCESS_INFORMATION
hProcess As Long
hThread As Long
dwProcessID As Long
dwThreadID As Long
End Type
Private Declare Function WaitForSingleObject Lib "kernel32" (ByVal _
hHandle As Long, ByVal dwMilliseconds As Long) As Long
Private Declare Function CreateProcessA Lib "kernel32" (ByVal _
lpApplicationName As Long, ByVal lpCommandLine As String, ByVal _
lpProcessAttributes As Long, ByVal lpThreadAttributes As Long, _
ByVal bInheritHandles As Long, ByVal dwCreationFlags As Long, _
ByVal lpEnvironment As Long, ByVal lpCurrentDirectory As Long, _
lpStartupInfo As STARTUPINFO, lpProcessInformation As _
PROCESS_INFORMATION) As Long
Private Declare Function CloseHandle Lib "kernel32" (ByVal _
hObject As Long) As Long
Public Sub ShellPause(Pathname As String, Optional WindowStyle As Long)
Dim proc As PROCESS_INFORMATION
Dim start As STARTUPINFO
Dim ret As Long
' Initialize the STARTUPINFO structure:
With start
.cb = Len(start)
If Not IsMissing(WindowStyle) Then
.dwFlags = STARTF_USESHOWWINDOW
.wShowWindow = WindowStyle
End If
End With
' Start the shelled application:
ret& = CreateProcessA(0&, Pathname, 0&, 0&, 1&, _
NORMAL_PRIORITY_CLASS, 0&, 0&, start, proc)
' Wait for the shelled application to finish:
ret& = WaitForSingleObject(proc.hProcess, 60000)
ret& = CloseHandle(proc.hProcess)
End Sub
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
It seems that if you're not specifying WindowStyle arg, the window will be
hidden when created. Have you tried specifying 1 as WindowStyle in your
ShellPause call?
-- Dev
<cgo...@gate.net> wrote in message news:7nsmk4$nir$1...@nnrp1.deja.com...
> I am using the code below (found on The Access Web I believe) to create
> a shell routine that pauses until the application is finished. The
> problem I've found is that this application works great when it is used
> in Microsoft Windows 95 or 98. However, when used in Windows NT 4.0,
> the application just hangs there - even after the application
> terminates.
>
> I'm thinking the fault might be the application. The application is
> called with a command file that tells the application to run minimized
> - could that in any way conflict with the WaitForSingleObject code?
>
> The code that is called in the function is:
> ShellPause "c:\iq\iqobject\iqpersnl.exe @g:\common\xray\XXX.cmd"
> (where xxx is replaced by the network login name through another API
> call)
>
>
>
> Here's the slightly modded ShellPause code:
<snip>