Page 1 of 1

Question about "limit result set"

Posted: Mon Apr 10, 2006 10:24 am
by FRED_EMMERICH_(Guest)
Is this feature the same as the "scope" from R&R DOS? It does not seem to work exactly the same. Obviously you cannot specify the lower value. I am using it against an indexed .mdb table (joined to one other on a one-to-many) and for example say I put in 100, I am not getting the first 100 indexed rows of data, I am guessing it is pulling the first 100 physical rows. I seem to recall the DOS scope value also was a counter on the master table and not on related tables, am I correct?____thanks__Fred Emmerich

=> Question about

Posted: Mon Apr 10, 2006 11:53 am
by kfleming
It is not the same as scope. Instead it returns the first 100 records that are actually read from the table. Note that this limit is only used for the current report in the designer and is not saved with the report for use in the next session.____Kathleen__R&R Support__

==> RE: Question about

Posted: Mon Apr 10, 2006 3:39 pm
by FRED_EMMERICH_(Guest)
Is there a way to limit the scope?

===> RE: Question about

Posted: Tue Apr 11, 2006 11:17 am
by kfleming
Not in the SQL version. You can only set a filter and then the backend database determines the method of record selection.____Kathleen__R&R Support

====> RE: Question about

Posted: Tue Apr 11, 2006 4:47 pm
by FRED_EMMERICH_(Guest)
In my case I was hitting a .mdb table, but the records being brought into R&R (no sorting) did not come in according to the index of the table in the .mdb. Is this normal? I thought it would honor the index keys.____thanks__Fred

=====> RE: Question about

Posted: Thu Apr 13, 2006 8:56 am
by kfleming
It is up to the ODBC driver itself to determine the order in which records are returned.______Kathleen__R&R Support__