Gustav Brock
gustav at cactus.dk
Wed Apr 24 01:35:02 CDT 2013
Hi Brad Rusty is right, I think. ODBC timeout is about not receiving anything for a while - no response - while time to retrieve data is another matter as long as data flows. That said, I've worked a little with Pervasive for a client of ours and - at least for some operations - it is terribly slow. So your situation could be that "that's just how it is". /gustav -----Oprindelig meddelelse----- Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Rusty Hammond Sendt: 24. april 2013 00:09 Til: Access Developers discussion and problem solving Emne: Re: [AccessD] How to Force ODBC Timeout Brad, It may have more to do with with how quickly the data starts getting returned by the ODBC database. Even though your front end query was taking a while, the data is being returned to the front end immediately so that part of the equation isn't timing out. Rusty -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: Tuesday, April 23, 2013 4:53 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] How to Force ODBC Timeout Rusty, Good idea. I will try to do this. I am starting to wonder if the ODBC Timeout value at the query level works differently for Pervasive than how it works for SQL Server. Thanks for your help. Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rusty Hammond Sent: Tuesday, April 23, 2013 4:51 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] How to Force ODBC Timeout Brad, Can you create a view (or query - not sure what pervasive calls it) in the Pervasive database that takes several seconds to run, then in your front end, create a linked table to that view and use this new linked table in your front end test query. Rusty