Access Timeout registry setting

Question

Access 2010 on Windows 7;

I am trying to create a table connection to a remote db but this connection times out at 60 seconds. How can I change the timeout?

Because this is not in a query, I am pretty sure I need to fix this in the registry. Any help appreciated.

Thanks!

Answer 1

Hi,

The message is from Microsoft Access:

ODBC-called failed.

[Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation

(#1013)

Years ago I received this sort of error, but it was actually from MS-Access not Oracle. MS-Access is only returning the server message because the server was told by Access to kill the query (user requested). Back then this issue was fixed by tweaking a registry setting. I've searched in my registry and can't find a timeout for Access in 2010.

Nothing has changed in our system as far as I know. I am on a functional-side team that interfaces with our IT area, so I would be informed if there were backroom changes being made. However, I can check with IT to be sure.

I did try changing the settings in Options under Client Settings but that did nothing, even after a close and reopen - I didn't however restart my computer yet... Also, maybe what I changed was wrong?

Answer 2

Take a look at: https://social.msdn.microsoft.com/Forums/en-US/b2acd61a-48cc-49e3-84dd-2babf6c39b3c/ms-access-2007-01013-timeout-error-oracle-10g-odbc-when-creating-linked-table?forum=accessdev it sound very similar to your problem and hopefully the same fix might help you.

Answer 3

Do you receive a specific error message?  If so, which one?  Please give us the No and Description.

There are a few settings that can be tweaked in the options -> client settings, but I'm not thinking they'd help in this case, but still worth looking at quickly.

Since you say this was working for a long time and suddenly stopped, you have to ask yourself what has changed.  If nothing on your end, then something has on the server/network, perhaps you need to inquire with the IT Dept to see if they can shed any light on the matter.

Answer 4

As I said in my original post, this is NOT a query - I cannot use a query.

I am connecting (as I always have) to an Oracle db with a user name and password. Navigation is EXTERNAL DATA tab then ODBC DATABASE then option LINK TO THE DATA SOURCE BY CREATING A LINKED TABLE.

Since this is not a query, I am pretty sure I need to change the registry, unless you know a better way?

This has not been a problem for the past three years until today.

Any ideas? - This is amazingly frustrating...

Answer 5

How are you connecting to the remote table? Are you creating a Link? If so, then I'm not sure you have much control over that.

You can create a Query that connects to the remote table, and you can set the ODBC Timeout value for that query. You must be sure to use a valid connection string in the query, of course. This property is set directly in the Query Properties.