Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / January 2007

Tip: Looking for answers? Try searching our database.

Unable to resolve 2147217865 (Invalid object name) Error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
EdAROC - 31 Jan 2007 14:13 GMT
Adding a file to a 2nd PC. Works on my PC (development) and on the live PC.
An SQL statement within VB module, SELECT ..., has the error. Removed and
re-installed MS Office 2000 (same on all PCs). Re-installed MDAC 2.81.
Checked ADO/DAO Library checkboxes in Tools (same configuration - checked and
sequence). Only difference is working PCs are on Windows XP, the problem PC
is 2000 - it is older hardware and cannot run XP.

Any suggestions to resolve this?
Dirk Goldgar - 31 Jan 2007 15:37 GMT
> Adding a file to a 2nd PC. Works on my PC (development) and on the
> live PC. An SQL statement within VB module, SELECT ..., has the
[quoted text clipped - 5 lines]
>
> Any suggestions to resolve this?

Could you show the code involved, and indicate what line of code is
actually raising the error?

Signature

Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Stefan Hoffmann - 31 Jan 2007 16:06 GMT
hi,

> Adding a file to a 2nd PC. Works on my PC (development) and on the live PC.
> An SQL statement within VB module, SELECT ..., has the error. Removed and
> re-installed MS Office 2000 (same on all PCs). Re-installed MDAC 2.81.
> Checked ADO/DAO Library checkboxes in Tools (same configuration - checked and
> sequence). Only difference is working PCs are on Windows XP, the problem PC
> is 2000 - it is older hardware and cannot run XP.
Are you using Access or VBA functions in your SQL like Left() or Nz()?
When yes, check the references, they may be broken.

Are you using With blocks with OLE automation? Is the Ole server still
active?

Has the failing PC the same language and country settings?

mfG
--> stefan <--
EdAROC - 31 Jan 2007 18:39 GMT
We discovered the problem. The ODBC connection configuration was not correct,
The default database was not pointing to the correct one.

Thanks for your replies.
 
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.