ODBC call failed

[Theblues]

Hi,

I have a standalone Access DB with 4 linking tables therein. They all point to tables that are stored in a server Access DB. I can open 3 of these tables in datasheet view without any problem, except one.
Whenever I try to open it, I am prompted following msg "ODBC call failed etc... server API error (#669) etc..."
And when I click OK to close the Error msg box, then another msg box appears with the msg: "Microsoft Access can't open the table in Datasheet view"

I've deleted the link table and recreated it. But I still can't open the table in datasheet view.
Does anyone knows what's to do?

 

[DrSnuggles]

Just a quick thought, to elimate the easiest option . . .

It could be a problem with the server db.
Can you open the table on the server db?
Possibly it has become corrupted.

I would repair the server db and try again.

 

[Theblues]

Thanks very much for your suggestion.
I'll try it and let you know if it has worked.

 

[Theblues]

Contrary to what I thought, I have discovered that the server DB is not an access DB as such. There is a hybrid operating system called Cache and developped by Intersystems that is installed on the server. Further, there is a SQL software (KB_SQL from the company above) running on that server by which means SQL tables are created. The table that caused me problems is one of them. So, these tables are not normal MS Access tables that can be opened directly from the server in a frontend, unless you run a select query.

Nevertheless, although I still can't open the link table in datasheet view from my standalone Access DB, I have tried to query it and have received a resultset. So it looks really like I can still query the table despite the mentioned issue.

Thanks anyway for your advice as it has helped me to dig deeper into the problem