[AccessD] Problem of a listbox's response on network... Part 1

I tried using ADO from Access to perform my SQL Server automation.  It worked but because of Access' 
single threading, when the query was running on SQL Server, the Access UI locked up tight.  Some of 
my queries take minutes or even hours.  Even though I was the only user, having the UI lock up like 
that left me wondering if the query was out to lunch or in fact ever going to finish.

I ended up moving to C# for that application, with threads and all that.  For that application, I 
was so much happier.  That does not address a user oriented form type application however.

At IBM I revisited ADO 'disconnected recordset' bound forms and controls and was quite happy with 
the results.

John W. Colby

Reality is what refuses to go away
when you do not believe in it

On 1/25/2014 1:00 PM, Jim Lawrence wrote:
> Hi Gustav:
>
> When I worked with ADO, all the queries, for the most part, were performed on the servers, as they should be, so there was no apparent performance losses. You may think the ADO was slow but it could sure out perform Oracle's Front End...so you are saying the bar was very low? ;-)
>
> Jim
>
> ----- Original Message -----
> From: "Gustav Brock" <gustav at cactus.dk>
> To: accessd at databaseadvisors.com
> Sent: Saturday, January 25, 2014 6:57:23 AM
> Subject: Re: [AccessD] Problem of a listbox's response on network...	Part 1
>
> Hi Jim
>
> I'm working on a large project using A2010 and SQL Server 2008 R2 as backend with ODBC connection.
> Recalling previous discussion about some "magic" of ADO, I tried to run some queries using an ADO connection but couldn't see any trend towards better speed so we left it there.
>
> Where we get into trouble with ODBC we use pass-through queries.
>
> /gustav
>