By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
462,924 Members | 599 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 462,924 IT Pros & Developers. It's quick & easy.

Getting in error on access application 2007

P: 222
Dear everybody,

I have designed a database on office 2007. I opened a report using layout view.

I am using CTRL + F option to find on the report the string that I want. Once I write the string on the box of search command I put search I am getting this error
access stop working and It is exiting from my application with the error code below :

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 12.0.6211.1000
Application Timestamp: 46d4aa81
Fault Module Name: MSACCESS.EXE
Fault Module Version: 12.0.6211.1000
Fault Module Timestamp: 46d4aa81
Exception Code: c0000005
Exception Offset: 001ae07f
OS Version: 6.0.6000.
Locale ID: 1033

Additional information about the problem:
LCID: 1033
Brand: Office12Crash
skulcid: 1033

Any Idea please help me. I have been working more than one week on the reports :( it was working well.

Thank you in advance

Jul 28 '08 #1
Share this Question
Share on Google+
2 Replies

Expert 100+
P: 1,923
This is the only problem with CTRL F that I could find on file:

Find Dialog
You should also be aware that the Find dialog (default form toolbar, Edit menu, or Ctrl+F) now exposes a Replace tab. This allows users to perform bulk alterations on data without the checks normally performed by Form_BeforeUpdate or follow-ons in Form_AfterUpdate. This seems highly undesirable in a database that provides no triggers at the engine level.

A workaround for this behavior is to temporarily set the AllowEdits property of the form to No before you DoCmd.RunCommand acCmdFind.


See this link for problems with layout view for reports:
Jul 28 '08 #2

Expert Mod 15k+
P: 31,770
I don't use A2007 so I don't have direct experience of this, but this looks to me like some form of corruption. Either in the database or in the installation of Access itself.
Aug 4 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.