[AccessD] Next, Prev

  It's a bit of a myth that Domain functions are slow.  An article ran in
Smart Access about 7 or 8 yeas ago that debunked this.  Domain functions can
be as fast as or faster then comparable DAO methods.

  If your looking for the ultimate in performance, you should test both
ways, otherwise use what's most convenient for you.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman
Sent: Friday, September 05, 2008 9:49 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Next, Prev

...and by a "lot" of data you don't mean a LOT of data ...ime DMin is slow 
even on a 10k record set ...I use Trevor Best's replacement module functions

which are much faster and work on everything from 97 to A2k3.

William

--------------------------------------------------
From: "Susan Harkins" <ssharkins at gmail.com>
Sent: Friday, September 05, 2008 8:50 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Next, Prev

> And it can be slow if you're dealing with a lot of data.
>
> Susan H.
>
>> I guess you could and should use DMin without any issues:
>>
>> NextItemID = DMin("ID","qryMyFormQuery","[Name] > '" & [Name] & "'")
>>
>> It will sort "correctly", that is the default sorting of your database. 
>> If
>> you need any other sorting the plot thickens.
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com