 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Queries / August 2008Can't access table Error Message from Microsoft Query
I have an Access db with many different queries. I tried connecting to one of the queries from within Excel using Microsoft Query and, although I can see the query in the table listing, when I select it to try and link to it, I receive the "Can't access table" error message. Has anyone come across this?? If the .mdb isn't open, open it and see if that corrects the problem.  SignatureSteve Clark, Former Access MVP FMS, Inc http://www.fmsinc.com/consulting > I have an Access db with many different queries. I tried connecting to one > of the queries from within Excel using Microsoft Query and, although I can > see the query in the table listing, when I select it to try and link to it, I > receive the "Can't access table" error message. > > Has anyone come across this?? Hello Steve, Thanks for your email response. Regardless of whether the db is open or not, I still get the same Microsoft Query error message, "Can't access table <query name>". Any other suggestions? Regards, Franklin > If the .mdb isn't open, open it and see if that corrects the problem. > [quoted text clipped - 4 lines] > > > > Has anyone come across this?? Hello Steve, Thanks for your reply. I tried linking to the query with the db both open and closed, and get the same result, the Microsoft Query error message "Can't access table <query name>". Any other suggestions? REgards, Franklin > If the .mdb isn't open, open it and see if that corrects the problem. > [quoted text clipped - 4 lines] > > > > Has anyone come across this?? You can fixed it by modifiying field names in Access (remove space in field names) then the export Access table. In your case, you are trying to connect to the Access table directly, so you should try to modify the Access table's field name structure to eliminate any spaces, and also make sure there is no "redundancy" in field names. I hope you will not get this error again. If you still get this error it means your database is damaged. In this case you can use compact and repair utility or Stellar Phoenix access recovery software. Download it:http://www.repair-access-file.com Hope it helps.. > Hello Steve, > [quoted text clipped - 16 lines] > > > > > > Has anyone come across this?? I rather doubt this means the MDB is corrupt. >If you >still get this error it means your database is damaged. In this case you can >use compact and repair utility or Stellar Phoenix access recovery software. You also work for that company. Posting without disclosing any connection is highly unethical and sleazy. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ You can fixed it by modifiying field names in Access (remove space i field names) then the export Access table. In your case, you are tryin to connect to the Access table directly, so you should try to modify th Access table's field name structure to eliminate any spaces, and als make sure there is no "redundancy" in field names. I hope you will no get this error again. If you still get this error it means you database is damaged. Hope it helps.. Franklin Smith;2790146 Wrote: > Hello Steve, > [quoted text clipped - 12 lines] > - > If the .mdb isn't open, open it and see if that corrects the problem. -- lack32 Thanks to everyone for the suggestions. The issue had to do with the "dreaded" Nz function, which Access of course likes, but Excel "chokes" on. It was the presence of that function within a calculated field in a subquery, that made the entire query unable to be accessed via Microsoft Query from within Excel. Franklin > You can fixed it by modifiying field names in Access (remove space in > field names) then the export Access table. In your case, you are trying [quoted text clipped - 23 lines] > > - > > If the .mdb isn't open, open it and see if that corrects the problem. > Thanks to everyone for the suggestions. > > The issue had to do with the "dreaded" Nz function, which Access of > course likes, but Excel "chokes" on. Not just Excel, of course: any application using ODBC or ADO to connect to a .mdb file will fail to execute a query containing that function. And it's not just Nz: do a search at support.microsoft.com using the keywords jet and sandbox to see the other affected VBA functions. In addition, user-defined functions are barred as well ... grr. SignatureMicrosoft MVP - ASP/ASP.NET Please reply to the newsgroup. This email account is my spam trap so I don't check it very often. If you must reply off-line, then remove the "NO SPAM" Thanks very much Bob. I learned something new today.... Franklin > > Thanks to everyone for the suggestions. > > [quoted text clipped - 7 lines] > > In addition, user-defined functions are barred as well ... grr. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.