If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > PC based Database Applications > Microsoft Access > ODBC connection to Access database

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Dec 2004
Posts: 74
ODBC connection to Access database

Hi,

I am trying to connect to an Access database located on another server using an ODBC connection over the network but each time I try to connect the following error is thrown:

'The Microsoft Jet database engine could not find the object......'

Anyone know what I am doing wrong and how to fix it?

Thanks
Reply With Quote
  #2 (permalink)  
Old
Registered User
 
Join Date: Dec 2004
Posts: 74
I also wanted to note that I am selecting the Access database using a Mapped Drive on my machine, not sure if this is the problem or not.
Reply With Quote
  #3 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
You shouldn't need an ODBC Connection to connect to another Access Database. Select File -> Get External Data -> Link Tables (leave the file type as Microsoft Access *.mdb; *.mda; *.mde) and then navigate to the mdb/mda/mde file and click Link. You should then see the tables in the mdb/mde.

If you still can't get it to work, try copying the mdb to your local drive and then linking the tables. It could possibly be a problem with the mdb (Compact/Repair the mdb to make sure.)

I've normally used ODBC Connections to connect to a server database such as SQL Server. Otherwise if you're having problems with the ODBC Connection for an Access Database, you can try re-installing/updating the MDAC. Also make sure you have permissions to that drive/folder and the Access mdb. The mapped drive shouldn't be giving you a problem but you can try re-mapping the drive.
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Last edited by pkstormy; 04-03-08 at 13:56.
Reply With Quote
  #4 (permalink)  
Old
Registered User
 
Join Date: Dec 2004
Posts: 74
Thanks for the reply pkstormy but I should have been a little clearer on what I am trying to use.

I am trying to run a Cognos report that connects to the Access database on the other serer using the ODBC connecting via a mapped drive, and thats where I am getting there error, trying to establish the connection. The mapped drive is ok, and the ODBC connection created without issue, but I can't seem to use it to pull back the data.

Thanks
Reply With Quote
  #5 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
hmmm...ok...I think I understand. So you're not actually trying to link the tables into another Access mdb but instead into a Cognos Report program? (sorry but I don't really have any experience with Cognos report software)

Here's some general troubleshooting things I can offer:

1. Make sure the mdb is compacted/repaired as the error you stated could mean a problem with the mdb itself.
2. Perhaps copying the mdb to a non-networked or another network drive, creating another ODBC Connection to that mdb and eliminating the mapped drive as a problem.
3. Create a new mdb and import the Access tables to that new mdb to make sure the mdb system object table is not somehow corrupt in the current mdb.
4. Try using a File DSN if using a System DSN (or vice-versa) as the connection (or OLE DB).
5. Select a different driver for the ODBC Connection or search for a Cognos-Access type driver (I had to select a special driver once to connect to a Progress backend db with Access.)

I'm assuming that the Access database opens ok and is not corrupt but I'd still run the compact/repair just to make sure (or import to a new mdb.)

Again, sorry but that's the best I can offer without knowing Cognos. Maybe someone else can chime in that's got more experience in this area. Hope this helps a little.
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Last edited by pkstormy; 04-03-08 at 13:53.
Reply With Quote
  #6 (permalink)  
Old
Registered User
 
Join Date: Dec 2004
Posts: 74
Thanks, I'll check out what you mentioned.
Reply With Quote
  #7 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
Spence23,

I'm curious on what you find is the problem. If you find a solution, would you mind posting it?
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)
Reply With Quote
  #8 (permalink)  
Old
SPAMMER
 
Join Date: May 2008
Posts: 10
Hi,

Have solved your problem yet? If not, I think you may check your mdb file, maybe it is damaged or something. If the file is unfortuantely damaged and you don't have a backup, you can try a utility called PancakeBunniesAreBetterThanSpam to repair your Access MDB file. It works rather well for my corrupt Access MDB files. Hope this helps.

Alan

Last edited by gvee; 06-26-08 at 10:10.
Reply With Quote
  #9 (permalink)  
Old
Registered User
 
Join Date: May 2003
Location: UK
Posts: 233
Are you able to connect anything to the Access db through the ODBC driver you have created. ie Crystal, Excel or is it a problem specific to Cognos?
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On