By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,560 Members | 1,093 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,560 IT Pros & Developers. It's quick & easy.

Running an update query through ODBC connection doesn't work

P: n/a
Our company has a collection system with a list of accounts in it, I
connect to this system with access using an ODBC connection. I pull in
the account #'s and other fields, then I have to run and update query
to update other fields from another table in our collection system. I
am able to update every field except for one and it gives me unknown
error -7776, then the help with says error 3000. It won't update this
one field for about 35 to 40K records. Does anyone have any idea why
this would happen or what I could do to fix it. Let me know if you
need more details...

May 24 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Mike,

Depending on what system your backend tables are on, if it is another
Access DB or Sql Server, I would use ADO to update your tables. I would
use ADO for everything. If it is a DBF system, you could use a pass
through query with ODBC. You can find several examples of pass through
queries on the internet.

Rich

*** Sent via Developersdex http://www.developersdex.com ***
May 24 '06 #2

P: n/a

Rich P wrote:
Hi Mike,

Depending on what system your backend tables are on, if it is another
Access DB or Sql Server, I would use ADO to update your tables. I would
use ADO for everything. If it is a DBF system, you could use a pass
through query with ODBC. You can find several examples of pass through
queries on the internet.

Rich

*** Sent via Developersdex http://www.developersdex.com ***


Found the problem, information in that field was corrupted and when
ever it hit information from a corrupted field it gave that error. As
soon as I cleaned out those fields everything worked fine. Thanks

Jun 14 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.