Note: You don't so much clear the bit, as not actually ever set it in
the first place.
At 03:15 AM 3/22/2009, you wrote:
Subject: RE: cannot clear dmRecAttrDirty bit, help please
From: Darren adelph...@yahoo.co.uk
Date: Sat, 21 Mar 2009 03:01:27 -0700
X-Message-Number: 1
am using DmReleaseRecord
am using DmReleaseRecord() to close the record directly after DmWrite() is
finished writing the records.
Cannot find any other function that closes records ?
It appears like the database is protected by the system, as no record
attributes can be changed ?
Darren
--
For information on
have tried DmReleaseRecord() in a loop, 0-maxrecords-1,
before database close which is before application quit.
-Does not work.
So have tried using DmSetRecordInfo() to set other record attrs.,
but they do not work either ?
So, nvfs(nand), involves the database being backed up to the non-volatile
you only need to close records you opened.
and stop blaming nvfs, as bad as it may be, YOUR problems are far
greater, and not related to nvfs
Best Regards,
Dmitry Grinberg
(847) 226 9295
On Fri, Mar 20, 2009 at 9:42 AM, Darren adelph...@yahoo.co.uk wrote:
have tried DmReleaseRecord() in a
I felt like saying that myself. The bit about NVFS, that is.
-Original Message-
From: Dmitry Grinberg [mailto:dmitr...@gmail.com]
Sent: 20 March 2009 18:20
To: Palm Developer Forum
Subject: Re: cannot clear dmRecAttrDirty bit, help please
you only need to close records you opened
if (attrdmRecAttrDirty)
attr = ~dmRecAttrDirty;
still no success.
have tried dmNewHandle/dmAttachRecord.
dmAttachRecord() sets the dirty bit.
Using a resource editor it is possible to change the bit.
many thanks for help
regards
Darren
--
For information on using the ACCESS Developer
Darren adelph...@yahoo.co.uk a écrit dans le message de news:
187...@palm-dev-forum...
Have a look at
Err DmReleaseRecord (DmOpenRef dbP, UInt16 index, Boolean dirty)
Purpose
Clear the busy bit for the given record and set the dirty bit if dirty is
true.
--
Regis St-Gelais
www.laubrass.com
no success,
1) attr = ~dmRecAttrDirty;
after the record has been written, does not work.
2) have tried both
attr = ~dmRecAttrDirty
and
attr = 0;
in a loop (0 to max records-1) at application stop, before the database is
closed. Also does not work.
many thanks and
regards
Darren
attr-=dmRecAttrDirty;
Please use
attr = ~dmRecAttrDirty;
as /subtracting/ is not the appropriate method to clear a bit!
However, did you try to clear the bit after releasing the record? It's quite
likely that the OS saves the dirty bit at some intermediate location.
HTH
Bodo
--
For
I am not sure if you tried this, but I am sure that you should change the dirty
attr after MemHandleUnlock, and after DmRelease record, and probably after
DmInsertionSort (just you will first have to find the record, since the index
has changed during the sort. Use the id).
Lionscribe
--
For
1) The goto statement is useful for 'code optimization' (reducing byte size of
.c source files).
X amount of returns incase of errors means having to, for example,
-reset draw state before return
-close and/or release any number of handles/ptrs
-close open files/ filestreams/databases
- etc.,
Hello (Palm TX/nvfs)
am trying, unsuccessfuly, to clear the dirty bit on new records
(records that dont need syncing, etc.), have tried a few methods, please see
following code :
// ••
// RecordAdd
Int8
RecordAdd(Global *GLB)
{
// text from fields
ASCII nameF[20];
First of all, why are you using goto? Didn't that die with BASIC? There are
1000 better ways to structure your code than goto statements.
Second, imo dirty bit is used as information for [rogram, and isn't really
changed by it, only by the APIs.
See
13 matches
Mail list logo
