Does anyone know what causes this message - ODBC--call failed

The full message is :
[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine  
Interface]S1T00Timeout expired.  

I can stop the message occuring by following instructions given:
http://www.pervasive.com/kb/kb.asp?solid=00016461 

BUT what actually causes the delay ...

Is it that
1. the server is not quick enough
2. the drives are not quick enough
3. someone else is holding the record and the ODBC link is waiting to read the record and times out
4. anything else

Thanks
Paul


Paul BurrowsAsked:
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.

GRayLCommented:
http://www.dbforums.com/showthread.php?t=436735

Does the anwer by PepGonzales trigger anything?
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
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I could be any number of those items, or it could be (as the link by Ray points out) that you're returning too large of a recordset.

Are you using bound forms? If you are, then your #3 could occur. If this becomes a common problem, you may need to move over to unbound forms, which would pretty much eliminate that scenario.
0
Paul BurrowsAuthor Commented:
The record counts of the ODBC linked tables are:
INTRX = 5,653,099 records
INLOC =  12,044 records
The 3rd table generated by a query [520-0 Unique Itemkeys] contains 3,625 records

I am actually unsure how many records will be returned ... a rough guess would be about 150,000.

What is a "bound form"?  How do I move to unbound forms?
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Assuming you're using an Access interface:

A bound form is one where you've set the .ControlSource of your controls (textboxes, combos, etc) to an underlying column in the form's Recordsource. To move to unbound, you'd need to (a) remove all .Controlsources from your controls and (b) handle all data manipulation via code. It can be a difficult process and if you're not familiar with it you might want to read up on it a bit.

Are you using a pass-through query for this? Or is this query built in Access as a "normal" query?
0
Paul BurrowsAuthor Commented:
No, I am not using a pass through query for this.  Grayl has pointed out elsewhere that this is an option.

I guess the problem is I simply have too many records.
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.