asked on

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

ASKER CERTIFIED SOLUTION

GRayL

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Paul Burrows

ASKER

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?

Scott McDaniel (EE MVE )

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?

Paul Burrows

ASKER

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.