> If you're writing to a database record, you have to use DmWrite (and
>company), which handles unlocking/relocking the record and does some
>bounds-checking to make sure you don't run off the end of the record. To
>protect the user's data, there is no supported way to write directly to the
>memory which represents a database record.
Just for my own information, is it really true that DmWrite handles
locking and relocking of the memory? I didn't know that. If so, I've
been wasting calls all this time...
