I've learned a few things in the last week about how carelessness in setting selector trigger labels and form titles within your code can overwrite other form resources producing bus errors, missing "object not in form" errors, disappearing objects, or objects that stop working. The solution I know for this is to enter sufficient text in the resource as a placeholder. But I'm finding this doesn't always seem to solve the problem.
My newbie-ish question is whether there is a more reliable way to ensure that form resources don't get corrupted by dynamic changes to the UI. Or even just to find out exactly how they are being corrupted so I can trace the source of the problem. This time the problem comes after I've added to a form that was working fine a group of pushbuttons and some handling code to set their value from the current record. The app works fine in POSE with an OS3.5 debug ROM, but I get the old "object not in form" fatal error when I try to pull up that form on my Handspring Visor. The objects are in the form according to Constructor (and POSE, apparently). Is there a more general approach to solving this kind of problem? David Beers -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
