on 8/23/00 5:32 PM, Steve at [EMAIL PROTECTED] wrote:
> Under random and infrequent (once an hour type frequency) circumstances,
> a user using our software on a Symbol SPT 1500 and scanning items (which
> are then looked up is gettings DataMgr errors involving "resizing
> record." However our software doesn't DO any resizing of records. Is
> there anything else which could cause this error?
There may be other reasons that DmResizeRecord() getting called - are you
allowing the user to edit records in place (with FldSetText(), for example)?
Or how about if the user updates an existing record with new data - how are
you handling the change in storage size requirements?
A common error that affects DmResizeRecord() is attempting to use a locked
record (inadvertently leaving it locked from a previous access). There are
the other usual suspects as well, such as bad index, corrupted DmOpenRef,
etc. (but I'm sure you've already checked these).
If you have the OS sources, do a search on DmResizeRecord() and see where it
pops up - it might tell you more about why it is being called.
JB Parrett
Palm, Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
