Nov 11, 2004 #1 Onyxpurr Programmer Feb 24, 2003 476 US I have a database that another location copies and places on their file server. When they copy it over, the odbc timeout of 600 is reset to 120 and my users can't run the report. Has anyone else had this problem? Anyone know of a fix? Thanks!!
I have a database that another location copies and places on their file server. When they copy it over, the odbc timeout of 600 is reset to 120 and my users can't run the report. Has anyone else had this problem? Anyone know of a fix? Thanks!!
Nov 11, 2004 #2 SonOfEmidec1100 Technical User Aug 12, 2001 965 AU Maybe the Timeout value is set in the registry. Depends on the version but something like \HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\QueryTimeout And/Or \HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\LoginTimeout Upvote 0 Downvote
Maybe the Timeout value is set in the registry. Depends on the version but something like \HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\QueryTimeout And/Or \HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\LoginTimeout