Tim,
I think the problem you are experiencing is that 3.5 refreshes a table more
often than earlier OS's. This causes your CustomDrawProcesure's to be
called when you do not expect it. They may be called at a time your record
is no longer available (eg after a delete) to refresh the table. When this
happens, you get the errors you've mentioned. (A big PITA to work around)
-Ken
> ----------
> From: Timothy Astle[SMTP:[EMAIL PROTECTED]]
> Reply To: Palm Developer Forum
> Sent: Wednesday, August 09, 2000 11:32 AM
> To: Palm Developer Forum
> Subject: OS 3.3 vs OS 3.5
>
> I just ran into an OS difference problem, and I'm not certain as to why.
> I
> was using OS 3.3 in most of my development, and I just recently did a test
> on a 3.5 Rom.
>
> The problem I'm getting is that whenever I use a DmRemoveRecord or
> DmDeleteRecord on the last record listed in my table, I get the following
> error. I can delete other records with no sweat. (weird...)
>
> MemoryMgr.c, Line:4340, NULL handle
>
> This confuses me because this code should work, and it's been working on
> OS
> 3.3 with no problems. I noticed that Nick Torenvliet mentioned upgrading
> to
> 3.5 and running into similar problems, but he cited Dialog boxes as a
> possible culprit.
>
> +++++++++++++
> Timothy D. Astle
> Embedded Systems Programmer
> ALT Group Inc.
> +++++++++++++
>
> "People who can smile when things go wrong has thought of someone else to
> blame it on."
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
> please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
