WHY DOES ACCESS 2007 SHUT DOWN WHEN I TRY TO RUN A QUERY OR OPEN A

[Guest]

have just installed office 2007 on new machine - when i try to open some
tables or run a query access drops out - HELP PLEASE !!!!!!!

 

[Guest]

Sounds like you have a corrupt installation. I would do the following steps:

1.) Uninstall Office 2007.
2.) Run Disk Cleanup to remove temporary files and such.
3.) Run the Disk Error checking utility to mark any sectors on your hard
drive that might be defective.
4.) Defragment your hard drive.
5.) Try re-installing the software.

Good Luck,

Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Guest]

Add me to this problem list.

 

[Guest]

Hi Sandy and RJM,

Are both of you trying to just open existing tables, or brand new tables? If
brand new tables, are you creating them in design view or by attempting to
use a table wizard? Same question regarding queries--brand new or existing
(sounds like existing queries, since the subject includes "try to run a
query", but I just want to check).

If you have antivirus software running, try temporarily disabling it. I have
heard of problems with antivirus software interferring with wizards in Access.


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Guest]

In my case I am running existing queries that include linked tables, linked
via ODBC to a Progress database. The Progress version was recently upgraded
to Open Edge 10.

 

[Guest]

Did this problem start immediately after the upgrade? Are you getting an
error signature message, that includes a command button to report the error
to Microsoft? Also, which operating system are you using? (I don't really
know the cause of your problems, but I can pass all details along to my
contacts at Microsoft).


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Guest]

Here are the details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 12.0.4518.1014
Application Timestamp: 4542815c
Fault Module Name: StackHash_111d
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Additional Information 1: 111d
Additional Information 2: d011f54793179db129e7a7911ec7aa5c
Additional Information 3: 1fc6
Additional Information 4: 00ac4b881d0d42eb179039aa0452216c

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

I am running Vista Business. It did seem to begin after the upgrade. The
odd thing is that I use these queries as a data connection in Excel in order
to dopivot tables and those work fine. Vista gives me the option of
reporting it, which I have done.

Thanks for your help.

Sandy

 

[Guest]

Sandy, would it be possible for you to get me the bucket number for this
crash?

1) Start --> Run
2) Right click Computer --> Manage (click Continue if you are prompted)
3) Select Event Viewer from left pane
4) Expand Event Viewer --> Widnows Logs and select Application
5) Look for an Error with event ID of 1000 or 1001 near the top of the list
6) Open this event and find the bucket number in the text for the event

Thanks!
-Zac.

 

[Guest]

Fault bucket 352169044, type 1

Thanks.

Sandy, would it be possible for you to get me the bucket number for this
crash?

1) Start --> Run
2) Right click Computer --> Manage (click Continue if you are prompted)
3) Select Event Viewer from left pane
4) Expand Event Viewer --> Widnows Logs and select Application
5) Look for an Error with event ID of 1000 or 1001 near the top of the list
6) Open this event and find the bucket number in the text for the event

Thanks!
-Zac.

 

[Guest]

Super, thank you Sandy! FYI it looks like this is the #54 most commonly hit
crash in Access 2007 accounting for about 0.3% of all crashes.

Can you send me a copy of your database packaged up in a .zip?
(e-mail address removed)

 

[Guest]

Well, it has all those linked tables and to the extent that it has data in
it, it is confidential financial information.

 

[Guest]

Okay, well it can be pretty hard for us to figure out what the cause is
unless we have a way to reproduce the error here at Microsoft on a computer
which is set up for debugging. The watson bucket information is definitely
helpful, and we may at least be able to stop the crashing with that info.

Thanks for sending this on!

-Zac.

 

[Sandy]

I appreciate the fact thatyou would like to solve the underlying problem
long-term. Do you have any suggestions as to what I could try to resolve the
situation short-term?

Thanks.

Sandy

 

[Sandy]

Also, I tried to create a new database and link to one of the ODBC tables. I
hot a reserved error -7748, no message with this error.

Sandy

 

[Jman1018]

Sandy,

Did you get your issue solved? I'm having the same problem. I upgraded to
Epicor Vista 8.03.403 with the new Progress OpenEdge 1.01B database and now
when I try to connect using ODBC using MS Access 2000, I get the -7748 error
message. Epicor told me to try a new version of MS Access, but it looks like
you are having the same issue.

Any help would be appreciated.

Jody

 

[Sandy]

Unfortunately, no. I tried to repair the installation but that didn't help.
The database was in Access 2000 format and I converted it, but that didn't
help.

The odd thing is that I have an Excel workbook that uses the query to pull
data into a pivot table and it works as always.

Sorry I couldn't be of more help.

Sandy

 

[Jman1018]

Sandy,

I found the solution after I posted my comment to you. I went to
"www.progress.com/openedge/support" then picked "Using the KB" and typed
Access error 7748" and it returned document P116845. I just followed the
easy instructions and I'm able to connect using ODBC with MS Access 2000. I
can't figure out why Epicor couldn't help me.

Jody