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

Run-time error 3155 ODBC insert on linked table failed

P: n/a
jj
This is strange, I've got an Access database developed that transfers
records to and from a remote database via Linked Tables/ODBC. It works fine
when connected to the development server. Same Access database pointed to
the production database server adn it returns this error after a short
period of time.

It's not like it dies right away, it'll transfer say 2000 of 4000 records,
try again and it'll transfer 1000 or 4000 records. So it's not even dying
or timing out in the same time or number of records.

Any ideas what is causing this? Again, same access database, just pointing
to a different database server.
Please advise. I'm stuck and it's urgent this goes live.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
jj
Argh... I switched the connection back to the other server which has worked
fine all this time and then last night and this morning it's deciding to
time out as well. Same thing, sometimes it times out within a few minutes,
sometimes it'll run for an hour or so before timing out. The database
upload process is about 4 hours total.

Does anyone have any ideas?
"jj" <jj@test.net> wrote in message
news:%K*****************@twister.rdc-kc.rr.com...
This is strange, I've got an Access database developed that transfers
records to and from a remote database via Linked Tables/ODBC. It works fine when connected to the development server. Same Access database pointed to
the production database server adn it returns this error after a short
period of time.

It's not like it dies right away, it'll transfer say 2000 of 4000 records,
try again and it'll transfer 1000 or 4000 records. So it's not even dying
or timing out in the same time or number of records.

Any ideas what is causing this? Again, same access database, just pointing to a different database server.
Please advise. I'm stuck and it's urgent this goes live.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.