[comp.sources.d] mbase - some nasty problems! any ideas?

dab852@csc.anu.edu.au (Robert McArthur) (01/10/91)

I have been trying to use mbase to store numerical data and am
having problems with retrieval (and, I suspect, storage).  The
problem manifests when either I mb_sel from start to finish or
mb_sel a particular record.  All data is numeric and there is
only one index.

The symptoms are that, although all the data is actually stored
(I have checked this thoroughly!), it does not store it in the
order you may expect!  For example, for my index, 2016 is greater
than 3006!  This happens throughout the stored file!  The numbers
that should be close together are closish but not really ordered
(not numerically nor, as far as I can fathom, through any sane
ordering scheme!).  The second problem with this is that when trying
to retrieve are specific record, I get one that is close, but not
the one I want.  It dosen't, by the way, get the record from the
place where it should be if it were sorted correctly ie. it isn't
just a simple rearrangement during storage not being known when
retrieving (if that makes sense...).

Has anyone else had any problems like this? (Yes, I have right
justified my numerical fields)  The package is in a very usable
form - it's very nice to use strtok() to pull the various fields
out neatly!  I just wish it would work without having to hack it!
I have examined the source without going into great detail...no
luck yet.  'elp!
-------------------------------------------------------------------
Robert McArthur		Centre for Resource and Environment Studies
			Australian National University
rjm@arp.anu.oz.au					
Pegasus,PeaceNet,GreenNet= peg:robert			S.D.A.