I posted the following message on 2/21/2002 (subject: PalmSim / 5.0 ??)

**** START REPOST

This code has been running perfectly fine on Palm OS 3.1 through 4.0 in POSE
3.4.

<snip>
// Open the resource database for read/write
tmpDBH = DmOpenDatabase(cardNo, dbID, dmModeReadWrite);
if (tmpDBH == NULL)
{
err = DmGetLastErr();
AbandonUpdates();
return (err);
}
<snip>

In PalmSim with Palm OS 5.0, I get an error code 534
(dmErrAlreadyOpenForWrites).

OK, so what's unusual about this ??

Well, I'm updating my own .prc. Yes, I need to.

**** END REPOST

After much interaction with a 5.0 developer (name withheld to protect the
innocent), we determined my application actually runs absolutely wonderful
on PalmSim and 5.0. As long as the Debugger isn't involved, that is. Which
took quite a while to figure out, because I was the only way I was testing
my app was while running under PalmSim and 5.0 from the debugger so I could
trap "surprises".

So, my application that runs fine from the Debugger with POSE 3.4 (and any
version of Palm OS up to 4.1) has a problem with the Debugger and
PalmSim/5.0. It appears that the Debugger is opening the .prc with Write
access, and leaving it that way for the duration of the debug session. So,
my application code listed above trips on the "DmOpenDatabase" function.

My very patient 5.0 developer contact suggested I contact MW, and in
particular, Ben Combee, via this newsgroup to report the ... situation ??

Regards,

Terry



--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/