That was my understanding of DB.field also.
I haven’t taken the Performance Tuning class. Does the class cover what the difference is between TR and DB and when to use either one? DB may be an efficient search but still a search where as TR would not be a search, correct? Even searching by the known record number in a really large table still could take some time. Multiply that by tens of thousands of records in the import scenario and it really starts adding up. Jason From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Wednesday, October 03, 2007 9:09 PM To: [email protected] Subject: Re: Filter Problem DB.Field has to query the database. By definition it is the data that's stored in the field in the database. >From my Performance Tuning class several years ago, Lincoln noted that it was >an efficient search because the record number is already known. Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
