Access 2010 query error
I was working with a DB in Access 2010 and went to modify a query. However when you click on the query the View button on the Ribbon does not light up. You have to run the query then the button becomes active. Well, this query has an error due to linking with an Excel workbook. I can't find a way to get into the query to fix the problem, at least in 2010. I fired up 2003 and had no problem selecting the query then clicking on Design.
Any Ideas? :cheers:
Update: this behavior only happens w/queries that have errors!
What if you right click it and choose Design View?
Originally Posted by ruirib
I had tried right clicking but got no response?
Unfortunately, I cleared the problem and now need to break a query to retest. :lol: :cheers:
No surprises there, because I created a bad query just to see what was happening :D.
Originally Posted by RetiredGeek
I get a normal menu, with the option to choose Design View (and others), when I right click the problem query. Maybe your situation is even more specific and it depends on the type of error you were experiencing?
Ok, I made it happen again. I renamed the Excel file that was linked to the query. I got the error below when I tried to run the query and then the Right-Click would not work. Renamed the Excel file back and everything works again. Go Figure. :cheers:
Update: Actually, the Right-Click doesn't work on any of the queries. I have this database locked down a bit so I'll need to check the settings, funny it doesn't affect it when opened in 2003.
I tried something similar. Linked to an excel sheet then created a simple select query over that linked table. Once that was done, renamed the excel file. Got precisely the same error message as you did, but my right click works and I could go into Design View.
Does the right click work for you for a "normal" query?
Ok, I found the problem and discovered a new one...
I had the Allow Default Shortcut menus turned off see below.
However, this particular error (when the Excel file is missing) causes the following message to appear. :cheers:
While we're on this topic of problems w/2010 here's a TechRepublic article I found useful. :cheers:
I see your problem, RG. In the few instances I had encounters with such errors, if memory does not fail me, I ended up deleting the query and recreating it.
There could be another way, a bit geeky, I guess, but that should suit you :).
You can have programmatic access to the query, print its SQL and even change it, after correcting any syntax errors.
Other than doing this, I really don't know how to solve it.
The article is interesting :). Thx.