Link SQL Server view into Access

SQL Server 2000, Access 2000

I have a SQL Server view that I linked into Access as a table. The view times out when either opened or used as the source of a report. I know I can create a query off of that view and set the timeout property in the query but I do not want to do that. Is there any way to set the timeout just for the table?

Thanks.
teneightyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SimonLarsenCommented:
Seems like you may want to have a look on sql as to why it takes so long (paste the view source into query analyser, turn on display execution plan run the query and then see what costs so much, maybe run the index wizard over it and see if that fixes it)

I don't know of a way to change timeout for just one but if everything else is working it shouldn't really matter should it? Just set it really high.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pique_techCommented:
I'm guessing, because I can't find solid documentation, that this particular timeout is set in the ODBC driver configuration.

The only way to change that, I think, is to edit the registry.  

I would strongly advise against it, in fact I'm unwilling to test it.

But if my hunch is correct, the relevant registry keys seems to be located at
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server\CPTimeout

Again, I think it would be *highly* inadvisable to change this unless you're absolutely certain you know what you're doing.  Messing around in the registry can render your computer UNBOOTABLE AND INOPERABLE.

Don't you think just running a query would be better?  It's certainly MUCH lower risk.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.