[AccessD] Next, Prev

Gustav Brock Gustav at cactus.dk
Fri Sep 5 12:27:21 CDT 2008


Hi William

Where do you "explicitly" see that? Did we read the same page?

These tests show comparable or - for the DAO and tabledirect methods - about 30% slower performance. That is not "notoriously slow". 
Of course, it may be important in some cases but quite often it doesn't matter - and you are done with one line of code.

/gustav

>>> wdhindman at dejpolsystems.com 05-09-2008 18:48 >>>
...except that your linked tests explicitly demonstrate that they are ...and 
in my own experience before I stopped using them, I almost always found them 
to perform poorly compared to the alternatives.

William


--------------------------------------------------
From: "Gustav Brock" <Gustav at cactus.dk>
Sent: Friday, September 05, 2008 10:50 AM
To: <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Next, Prev

> Hi Susan
>
> No secrets except for an index but that is common sense.
> Some tests are found here:
>
>  http://www.access-programmers.co.uk/forums/showthread.php?t=79622 
>
> As you can see, no basis for the usual statements like "the domain 
> aggregate functions are notoriously slow".
>
> /gustav
>
>>>> ssharkins at gmail.com 05-09-2008 16:29 >>>
> I've never used one that didn't make me wish I hadn't -- so Gustav and
> Jim -- share the secret of making them performance friendly????
>
> Susan H.
>
>
>> Hi Jim
>>
>> That is pretty much my experience too.
>>
>> /gustav
>>
>>
>>  It's a bit of a myth that Domain functions are slow. ..






More information about the AccessD mailing list