OHSU's Software Forum

onge · Joined: 28 Dec 2007 Posts: 1

I have worked on dozens of Access 2003 databases for years and just recently switched to 2007. I've been having the same problem as the people who posted below and know of no solution:

http://www.mcse.ms/showthread.php?t=2483267

http://www.mcse.ms/message2526566.html

http://www.mail-archive.com/ms_access@yahoogroups.com/msg03739.html

jordane · Joined: 03 Jan 2008 Posts: 1

The same thing just happend to me. I opened an exiting query that I've run successfully before a ba-jillion times and got this error message. I am unable to right-click and "Open" it or open it in Design View. The query even has "proper" naming convention, where-as others that do not use "proper" naming open and run. Most irritating.

armando · Joined: 06 Nov 2007 Posts: 11

i haven't been able to re-create this error yet.
do you have a database you could share where this is happening?

armando

Cindy · Joined: 02 Nov 2007 Posts: 1

I cannot replicate this error either.

Make sure that SP1 is installed, it should be but check just to be safe. Go to Access Options and click on the Resources category. The last resource listed is the About Microsoft Office Access 2007. Click on it to see if SP1 is showing.

If you changed your options and unchecked the Perform name Autocorrect check box you might get the error message. See below fix from Microsoft's knowledgebase.

I typed in "Access 2007 queries errors" and had to look thru most of the first page. It's the fourth link from the bottom.

Cindy Calderwood

CAUSE
This issue may occur when a table or a query has the same name as a form or a report in the Access 2007 database.

RESOLUTION
To resolve this issue, rename the form or the report so that it differs from the name of the table or the query.

Caution Name AutoCorrect fixes most issues that occur when you rename any forms, reports, tables, or queries. However, Name AutoCorrect does not repair tables, queries, or field name changes in macros or in code. Also, Name AutoCorrect does not track changes to form, report, or control names. You may have to fix some references manually. Therefore, make sure that you make a backup copy of the database before you make any changes.
To rename the form or the report in the database, follow these steps:
1. Click the Microsoft Office Button, and then click Open.
2. In the Open dialog box, select the database that you want to open, and then click Open.
3. If you receive the following message, click Options, click Enable this content, and then click OK.
Please enable code in this database using the security bar above or open this file from a trusted folder.
4. Click the Microsoft Office Button, and then click Access Options.
5. In the Access Options dialog box, click Current Database.
6. Under Name AutoCorrect Options, make sure that the Perform name Autocorrect check box is selected. If it is not selected, click to select the Perform name Autocorrect check box. Then, close and reopen the database for the change to take effect.
7. In the Navigation Pane, right-click the form or the report, and then click Rename.
8. Type a new name for the form or for the report, and then press ENTER.
9. On the Quick Access toolbar, click Save.

For more information about how to rename a form or a report, follow these steps:1. Click Microsoft Office Access Help, or press F1.
2. Type rename or delete objects in the Search box.
3. To view the topics, click Search.

Kamikaze · Joined: 17 Jan 2008 Posts: 1

I'm not a guru at this, so I am not sure "why" this works, but it seems to be a work-around for viewing in Design View.

If I right-click the Query, I get the error message. BUT, if you look at the bottom right corner of the window, there are icons for Table View, SQL and Design View. Click on that Design View and it will open right up. Strange.

That works for the design view but I have not figured out the import problem. You can always copy from Excel and paste right into the Access table. That works like a champ but it won't import the very same Excel data.

Hope that helps.
Jim

emc · Joined: 28 Oct 2008 Posts: 3

I just got off the phone with Microsoft and apparently this is a known bug (as of May, 2008). They gave me the reference number #37769.

They have not yet released a fix.