Since data size is an issue, you might just returning all the record _id fields and as you move back and forth, just query that one record and populate. If you have 17000 items at 8 bytes (largest storage for int size in SQLite), you would still only be looking at 136k worth of data. Most likely it will only be using 4 bytes for the int and the data load will be less.
Step forward, backwards, or to whatever record using the method you currently are, grab the _id, pull that single record, show record and you are done. Since you should be using that _id as a primary key, this should be lightning fast and have little or no delay on showing the record. Steven Studio LFP http://www.studio-lfp.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
