No...that example does exactly what I'm doing now. It pulls back all the records in the table that match the criteria of the SQL statement, and then only displays the one you're interested in displaying. I was seeking a way to only select a specific number of the records from the database and display all the retrieved rows, then select the next x records and display those. Unless I'm misunderstand how PHP works under the hood, this would improve performance. Instead of giving PHP the whole set of records to work with and using PHP to limit what is printed out, I wish to let the DB sort out what to give to PHP to print. DB servers are much better at that than scripting languages.

Then again, perhaps PHP's odbc_fetch_row() gets one row at a time from the DB server, instead of getting the row from a record set that odbc_exec() already pulled out (which is what I believe). I guess the real question is, what happens "under the hood" when the odbc_exec() funtion is executed.


- Chris
32GB MK2 090000664 Smoke
Queue # 2 (who the heck was 1?)