-=> Quoting mark lewis to Scott Adams <=-

 SA>>         Yeah for awhile I've been trying to get the right
 SA>>         Jam structures out ther eto do some quite proggie.
 SA>>         But unfournately theres alot of 3rd party stuff
 SA>>         out there to find the right format is difficult.
 
 ml>> actually, its not the datafile structures that are the problem(s)...
 ml>> it is the methods of accessing those datafiles and what stuff has to
 ml>> be done in what order and such...
 
 SA>         Well i can do the access stuff easy if i can just get
 SA>         the data file structures :)

 ml> i dunno... i guess it depends on what one is doing... an example is
 ml> editing a message... if you edit an existing message, a new header
 ml> record is created that points to the message body and the old header
 ml> record is marked deleted... when packing the base, the nondeleted
 ml> headers are copied to the new file and the message bodies that match
 ml> are copied to a new body file... pointers are adjusted as necessary... 
 ml> much easier to acquire the MKSRCMSG package... its got all this stuff
 ml> figured out and available already... there's even a sample program or
 ml> two... one of them "converts" message bases between those
available...
 ml> BTW: those are *.MSG (SDM), HMB, SQU, JAM, and old(er) EZYcomm... 


        Well what I'm wanting is rather simple compared to the
        file edits really.  HMB?  Never heard of that..oh wait..
        I seem to recall vaguely..where was it..man that
        must be a decade or more ago..where was it...hmmm..
        can't recall...

 SA> But those that I do
 SA>         have around here all have a bit of conflicting methods
 SA>         and structures slightly.

 ml> wierd... where'd you get them from?

        Actually just my collection of code 'stuff' over the
        years.  Plus the TG sources have it but for some
        reason its not well...structured :)


... "You want to tell me what it is?" - Garibaldi
--- Fringe BBS