[EMAIL PROTECTED] wrote in message <[EMAIL PROTECTED]>...
>
>Probably an artifact issue. I don't think she null-terminated her char
>arrays. So, if the old string is longer than the new one, she'ld be
>reading past the new one into the old one. Remember that she didn't
>DmResizeRecord() on the record either.
>
>Richard Hartman wrote:
>>
>> Wait a sec ... if the -old- data is larger you have the problem? I would
>> expect problems if the -new- data is larger ...
>>
>
>
She was using DmStrCopy() ... (checking docs) ... hey! Are the
docs
(http://www.palmos.com/dev/tech/docs/palmos/DataAndResourceManager.html#9274
35)
right?? This states that DmStrCopy() doesn't actually do any copying,
that it only "Check the validity of the chunk pointer for the record and
make
sure that writing the record will not exceed the chunk bounds."
If that is correct, then she still needs a DmWrite() in the pack routines.
If that is not correct, the the question remains as to whether DmStrCopy()
will write the terminating NUL or not. I was kinda assuming that it would
behave like StrCopy() and write the terminating NUL, but your response
implies that you think differently.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
