J
Jim
Access 2002 adp connected to SQL server, running through
terminal services. When I execute any command through ADO
(sample below), the cpu usage immediately jumps to 100%
and stays there. Needless to say all other users (3-4)
are dead in the water until the command is done. It
occurs whether I am executing a stored procedure or
passing a sql string.
Any ideas?
Dim cmd6 As ADODB.Command
6380 Set cmd6 = New ADODB.Command
6390 cmd6.ActiveConnection = cnnConnection
6400 cmd6.CommandText = "sp_WABillPrintUpdate"
6410 cmd6.CommandType = adCmdStoredProc
6420 cmd6.Parameters.Refresh
6430 cmd6.Parameters(1).value = Me!cboBillingGroup
6440 cmd6.Execute , , adAsyncExecute
6450 Do Until cmd6.state <> adStateExecuting
6460 Loop
6470 Set cmd6 = Nothing
terminal services. When I execute any command through ADO
(sample below), the cpu usage immediately jumps to 100%
and stays there. Needless to say all other users (3-4)
are dead in the water until the command is done. It
occurs whether I am executing a stored procedure or
passing a sql string.
Any ideas?
Dim cmd6 As ADODB.Command
6380 Set cmd6 = New ADODB.Command
6390 cmd6.ActiveConnection = cnnConnection
6400 cmd6.CommandText = "sp_WABillPrintUpdate"
6410 cmd6.CommandType = adCmdStoredProc
6420 cmd6.Parameters.Refresh
6430 cmd6.Parameters(1).value = Me!cboBillingGroup
6440 cmd6.Execute , , adAsyncExecute
6450 Do Until cmd6.state <> adStateExecuting
6460 Loop
6470 Set cmd6 = Nothing