ODBC error "could not open file <path>\dba.mdb"

[dryajov]

NOTE TO MODERATOR: I'm reposting this thread here, please remove the duplicate from ACCESS/VBA forum. Thanks.

Hi I'm not sure if this should go here in the first place, this is more likely an ODBC driver issue.

I'm having the strangest behavior when trying to do an insert into an access database from a C++ application, thru ODBC. I'm able to successfully open a connection to the DB and perform selects, but when I try to do an insert the strangest thing happens, ODBC throws an error saying that it can't open the "dba.mdb" file, which is not the db file I have established connection to nor it is mentioned anywhere explicitly in the code... I'm stumped, it looks like for some reason the ODBC driver or access itself is trying to load this db for some reason. Any clue why?
I have read/write access to the DB file I'm connected.. Also, I don't have Access installed on the PC, but don't think it has anything do with it, (but I'm no expert in this filed so I might be/probably wrong.)

Any help is greatly appreciated.

Thanks in advance

[dryajov]

NOTE TO MODERATOR: I'm reposting this thread here, please remove the duplicate from ACCESS/VBA forum. Thanks.

Hi I'm not sure if this should go here in the first place, this is more likely an ODBC driver issue.

I'm having the strangest behavior when trying to do an insert into an access database from a C++ application, thru ODBC. I'm able to successfully open a connection to the DB and perform selects, but when I try to do an insert the strangest thing happens, ODBC throws an error saying that it can't open the "dba.mdb" file, which is not the db file I have established connection to nor it is mentioned anywhere explicitly in the code... I'm stumped, it looks like for some reason the ODBC driver or access itself is trying to load this db for some reason. Any clue why?
I have read/write access to the DB file I'm connected.. Also, I don't have Access installed on the PC, but don't think it has anything do with it, (but I'm no expert in this filed so I might be/probably wrong.)

Any help is greatly appreciated.

Thanks in advance

Found the problem, all the queries had a dba prefix to the queried tables, so the ODBC driver was getting confused by it. The strange thing is that this functionality was working unmodifyed for more that 5 years on the same versions of OS... No clue of why it stopped working all of a sudden.

[sicarie]

No clue of why it stopped working all of a sudden.

Just out of curiosity, did it stop working ... oh, Wednesday morning?

(I'm thinking M$ Tuesday, here)