Question:
Why do I get a soft reset and nasty messages when I
call DmInsertionSort() after calling DmDeleteRecord() or DmRemoveRecord()?
The only reason I can think of for this is that maybe the
pointer to the database (returned by DmOpenDatabase()) is somehow
invalid after calling the DmDeleteRecord() or DmRemoveRecord()
functions. But the documentation gives me the impression that
the reference returned by DmOpenDatabase() is analogous
to the Unix FILE* pointer, so that it should not move around,
not matter what I do to the database.
The really strange thing is that if I call FrmCustomAlert()
in between deleting a record and sorting the database,
the problem goes away!
I don't see the connection here.
If no one recognizes this problem from their own experience,
I'll look into it more deeply.
But it looks to me like it shouldn't happen.
Cheers,
Alan Kennington.
--------------------------------------------------------------------
name: Alan Kennington
palmtop: Palm IIIx
palmdev: gcc/linux (redhat 5.2)
palmsrc: http://topology.org/src/palm/README.html
e-mail: [EMAIL PROTECTED]
city: Adelaide, South Australia
coords: 34.89744 S, 138.58970 E
pgp-key: http://topology.org/key_ak1.html
