Error when running Queries Access 07

[whplayer65]

I have ran into an unusual situation with a few of our newer computers. When they attempt to run a query most of the time it will result in MS Access crashing. Sometimes however the query will work. These computers are running 32 bit Windows 7 OS and Office 2007. Our older computers that are running Windows 7 32 bit and Office 2007 will run queries without a hitch. It just seems to be these latest 4 that are experiencing the issue. I have pasted the error report below. Any help would be greatly appreciated!

Log Name: Application
Source: Application Error
Date: 3/12/2014 11:30:30 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: testPC
Description:
Faulting application name: MSACCESS.EXE, version: 12.0.6606.1000, time stamp: 0x4e27ab6b
Faulting module name: MSVCR80.dll, version: 8.0.50727.4940, time stamp: 0x4ca2b271
Exception code: 0xc0000005
Fault offset: 0x000172d7
Faulting process id: 0xe10
Faulting application start time: 0x01cf3e079ac33539
Faulting application path: C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a 1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCR 80.dll
Report Id: 3e35cd02-a9fb-11e3-b82b-f8b156c4ddb4
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>


<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-03-12T15:30:30.000000000Z" />
<EventRecordID>1705</EventRecordID>
<Channel>Application</Channel>
<Computer>otics00675.oticsusa.com</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>12.0.6606.1000</Data>
<Data>4e27ab6b</Data>
<Data>MSVCR80.dll</Data>
<Data>8.0.50727.4940</Data>
<Data>4ca2b271</Data>
<Data>c0000005</Data>
<Data>000172d7</Data>
<Data>e10</Data>
<Data>01cf3e079ac33539</Data>
<Data>C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc 8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc \MSVCR80.dll</Data>
<Data>3e35cd02-a9fb-11e3-b82b-f8b156c4ddb4</Data>
</EventData>
</Event>

[NTC]

one presumes that you have updated the Access 2007? I ask only in that it is not uncommon that "new installs" rely on an old cd - and then one forgets to immediately update the app....

otherwise is the suspect query one that is taking a particularly long time to cook ?

[whplayer65]

one presumes that you have updated the Access 2007? I ask only in that it is not uncommon that "new installs" rely on an old cd - and then one forgets to immediately update the app....

otherwise is the suspect query one that is taking a particularly long time to cook ?

Thank you for your response. Access 2007 has been completely updated. This install is a network install that we use for all computers (new computers or reinstalls). The query does take around a little longer than usual to run. This particular query pulls man hours from different departments, usually for an entire month.

[NTC]

Sanity Check: Your implementation is a split database with the FE on each PC - and the BE on a server or common PC folder available to all?....and both FE & BE folders have been set up to be trusted?

[whplayer65]

Sanity Check: Your implementation is a split database with the FE on each PC - and the BE on a server or common PC folder available to all?....and both FE & BE folders have been set up to be trusted?

The database is stored on a common folder that everyone navigates to in order to run the report.

[NTC]

The only correct, supported, multi user implementation is a split database with the FE on each PC - and the BE on a server or common PC folder available to all. If your implementation does not conform to this requirement then you have found the problem.

[whplayer65]

The database is sitting on a share, and office is installed on the end user computer. We have always done it this way and have not ran into an issue except for this latest batch of computers.

[NTC]

Have seen the statement "we've done it this way for....." - many many times. Doesn't matter. The correct installation is as per my prior post and for which you have no choice. The only variance to it that you can consider is for each user's FE can be on a share - - but there still has to be 1 FE per user and you cannot have 2 users opening the same FE at the same time. You actually have dodged a bullet in having such minor symptoms as it can corrupt the db entirely what you are doing.