I'm SO SO SO SO sorry. But as far as I remember using DmQueryRecord on NVFS has no the said so side efect if its used right.
In the case of my read-only example, you read and get the data from the record on the database, this data is cached, and you can copy that data into a stucture or allocated chunk of memory, you will not have a truncated record or scrap if you do not do another DmWhatever function that may force the cache to flush before getting the data, in such case you will have an invalid pointer. Both examples are working for me, and I'm sure of this because I'm a lucky one who do programming and debuging for, and on, NVFS devices, and I may be wrong but I never experienced a truncated record or such issues as you described. To everyone "The use of the pattern of query/lock/unlock it's the recomended way" (thanks to Ben Combee), and as I said I'm SO SO SO SO sorry to give you people incomplete threads, to make confusion, and to not EVER EVER EVER EVER be polite, I'll do my best to do the things right in future posts. Sincerely yours. Eduardo Orea. P.S: Ben Combee'n post about NVFS http://palmos.combee.net/blog/TheNVFSFilesHowSyncsCanFa.html "Dmitry Grinberg" <[EMAIL PROTECTED]> escribió en el mensaje news:[EMAIL PROTECTED] Do NOT EVER EVER EVER use DmQueryRecord on NVFS. Do not EVER EVER EVER listen to people who tell you to do so, they are either not familiar with NVFS, or lucky enough to not use or test on any of earlier NVFS devices. On all but the latest NVFS devices this can and WILL Cause random crashes in low-memory situations see my post to this very thread at "Wed, Jun 18, 2008 at 9:23 AM" for specifics as to why. ---- Best Regards, Dmitry Grinberg (847) 226 9295 -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
