ODBC--call failed

TBC

Registered User.
Local time
Yesterday, 23:56
Joined
Dec 6, 2010
Messages
145
I’ve been trying to do a basic pass thought query. But have been receiving these two error messages


1.ODBC--call failed. [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'my tabel name' (#102)
Error message

2. ODBC--call failed. [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'my tabel name' (#208)


Basic Query
SELECT dbo_VC_Admin.app_num
FROM dbo_VC_Admin;

When trying to open the server table
a. ODBC--call failed. [Microsoft][ODBC SQL Server Driver]Timeout expired (#0)


I don’t have access to change my regedit:
HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC

So Is there another way to fix this error?


Thanks for your help
 
Do you really have a table called my tabel name?

You spelled table wrong. That have something to do with it?
 
Sorry to revive an old thread. I have what I find to be a strange error occurring. Hopefully I can make this clear. When the database opens a form called frm_SysControlForm opens first. Then it opens frmMainScreen and frm_SysControlForm gets minimized. The form frmMainScreen has a button called "Exit Orders Database". If I click on that button the database closes without problems. If I click on red X in the top right corner I get an ODBC error. The error I'm getting is:

"ODBC-call failed.

[Microsoft][ODBC SQL Server Driver][SQL Server][Violation of PRIMARY KEY constraint 'aaaaaztblUsers_PK'. Cannot insert duplicate key in object 'dbo.ztblUsers'. The duplicate key value is (Garrett). (#2627)[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated. (#3621).

The table called ztblUsers is supposed to hold all the users that can access the database. Now, I didn't create this database or any of the tables. It wasn't my idea to make a name the apparent primary key.
 
This error isn't actually related to this thread. ODBC-call failed is a generic error message, the real error message is the one below that.

In your case, there's code being fired off when you close the form which attempts to INSERT into the tblUsers table but fails to do so due to referential integrity. So you need to find the code that does that and it could behind either forms.
 

Users who are viewing this thread

Back
Top Bottom