Dual Processor Computer Hangs When Running Query (178650)

SYMPTOMS

When you try to run a large, complex, select query or a large action query such as a make-table query on a dual processor computer, the query does not finish processing, and Microsoft Access stops responding (hangs). If you monitor the system, you see that the processor time drops to between 0% and 1% shortly after the query begins running. However, you can press CTRL+BREAK to terminate the query, and Microsoft Access functions normally. This behavior also occurs if you try to import a delimited text file that is 70 megabytes (MB) or larger.

You can run the same query or import the same text file on a single processor computer.

RESOLUTION

There are two resolutions and one workaround to this problem.

Install Microsoft Office 97 Service Release 2

Obtain and install the Microsoft Office 97 Service Release 2. For more information about getting this Service Release, see the following article in the Microsoft Knowledge Base:

151261 OFF97: How to Obtain and Install MS Office 97 SR-2

Install Microsoft Jet 3.51

Obtain Jet35sp3.exe from the Microsoft Web site; this file contains the updated version 3.51 of the Microsoft Jet database engine. For information about how to obtain Microsoft Jet 3.51, see the following article in the Microsoft Knowledge Base:

172733 ACC97: Updated Version of Microsoft Jet 3.5 Available for Download

To work around this problem, use only one processor if you intend to run large, complex queries or import large text files on a dual processor computer. Follow either of these methods to use only one processor.

Method 1

Press CTRL+ALT+DEL, and then click Task Manager.
Click the Processes tab.
Right-click MsAccess.exe, and then click Set Affinity.
Click to clear either CPU0 or CPU1.
Click OK, and then close Task Manager.

Method 2

Create a new database.
Create a new form.
Add a command button named Command0.
Click Code on the View menu.

Type the following code:

Option Compare Database
Option Explicit

Private Declare Function SetProcessAffinityMask Lib "kernel32" _
   (ByVal hProcess As Long, ByVal dwProcessAffinityMask As Long) As Long
Private Declare Function GetProcessAffinityMask Lib "kernel32" _
   (ByVal hProcess As Long, lpProcessAffinityMask As Long, _
   lpSystemAffinityMask As Long) As Long
Private Declare Function GetCurrentProcess Lib "kernel32" () As Long
Private Declare Function OpenProcess Lib "kernel32" _
   (ByVal dwDesiredAccess As Long, ByVal bInheritHandle As Long, _
   ByVal dwProcessId As Long) As Long
Private Declare Function CloseHandle Lib "kernel32" _
   (ByVal hObject As Long) As Long
Private Declare Function GetWindowThreadProcessId Lib "user32" _
   (ByVal hwnd As Long, lpdwProcessId As Long) As Long

Private Const PROCESS_SET_INFORMATION = (&H200&)
Private Const PROCESS_QUERY_INFORMATION = (&H400&)
Dim a As Object

Private Sub Command0_Click()

   Dim idThread As Long
   Dim idProcess As Long
   Dim ProcessAffinity As Long
   Dim SystemAffinity As Long
   Dim lRet As Long
   Dim hProcess As Long

   idProcess = Shell("C:\Program Files\Microsoft" & _
      " Office\Office\MSACCESS.EXE" & _
      " C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb", _
      vbMaximizedFocus)

   If idProcess Then
      hProcess = OpenProcess(PROCESS_QUERY_INFORMATION Or _
         PROCESS_SET_INFORMATION, False, idProcess)
      lRet = GetProcessAffinityMask(hProcess, ProcessAffinity, _
         SystemAffinity)
      ProcessAffinity = 1 ' this sets the process to only run on CPU 0
                          ' for CPU 1 only use 2 and for CPUs 1 & 2 use 3
      lRet = SetProcessAffinityMask(hProcess, ProcessAffinity)
      CloseHandle (hProcess)
   End If

End Sub

Save the form, and then open the form in Form view.
Click Command0.

MORE INFORMATION

Steps to Reproduce Problem

Start Microsoft Access on a dual processor computer and open the sample database Northwind.mdb.
Create a new query in Design view.
In the Show Table dialog box, click the Tables tab and select the Orders table.
Click Add twice so that the Orders table is added to the query twice, and then click Close. Do not create a join between the tables.
Drag the asterisk (*) from the Orders table into the query grid, and then drag OrderID from Orders_1 (the second instance of the Orders table) into the query grid.
On the Query menu, click Run. The query should return over 688,000 records.
On the View menu, click Design View.
On the Query menu, click Make-Table Query.
In the Make Table dialog box, type qryTestTable and click OK.
On the Query menu, click Run. Note that Microsoft Access stops responding before the query finishes processing.