>This does not change the ID's, and it doesn't appear >that NSB "backfills"
Correct; once the ID has been assigned by the NSB/Palm IDE, it doesn't compact them if you delete objects. Nor does it "backfill". It stores the highest ID it has used so far in the project, and increments from there as you add objects. >so if the last ID is 3500, getting rid of earlier objects doesn't mean that the >next ID is less than 3500. Correct. >So would I have to copy all of the existing forms to a new project to ensure >that I stay below 9999? If your current maximum ID is around 3500, then you have a long way to go before reaching 9999. But if the question is how you would "compact" the IDs after removing a ton of objects, then doing a copy & paste of the forms to a new project may accomplish that. I'm not 100% positive. It has been too long since I copied a form in NSB's IDE, so I can't remember for sure how it handles the IDs in the pasted version. I *think* it renumbered them from the then-current project maximum ID. >Would this solve the erratic problem of tapping on an object and then having >some random code be accessed? Do you have object IDs approaching 9999? From what I know of the NSB object ID paradigm (I've used NSB/Palm, but don't have inside company knowledge) I can see how you might have apparently random code get accessed. For example, object 11234 may end up invoking the code for object 1234. If your maximum ID was well below 9999, then I don't think this is part of your problem. Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
