Hi, > How about using DmFindSortPosition to figure out your insertion point.
All these issues related to 30,000 records have been on my mind recently. With the arrival of faster processors, I'm going to raise the record limit in one of my applications. I've been promising this to my users for a while now, so I need to follow through. I know the absolute limit (at least for now) is 64k records, and I can live with that. However, I know that certain APIs didn't really work in past versions of the OS, due to the use of Int16 instead of UInt16 variables internally. Someone earlier in this thread referred to list functions. (I assume these refer to functions like LstSetPosition, right?) I use tables rather than lists to display my data, so that's not going to be a problem for me. However, there are at least two areas I'm pretty sure will give me trouble: 1. DmFindSortPosition 2. Scroll Bar APIs For these APIs, I'd like to know: A. What is the minimum version of the Palm OS in which there are no problems with large databases? B. For prior versions of the Palm OS, at what limit did they start to break? For example, the answer might be something like (I'm making this up): Scroll Bars only worked correctly for 0-32k records until OS 3.5. Starting with OS 3.5, they work correctly for any number of records (0-64k). Lastly, are there other APIs/Controls/gotchas that only have problems with large databases? Thanks in advance! Tom -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
