Subj : *.msg format
To   : Scott Adams
From : mark lewis
Date : Wed Feb 26 2003 11:39 pm

 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 :)

i dunno... i guess it depends on what one is doing... an example is editing a 
message... if you edit an existing message, a new header record is created that 
points to the message body and the old header record is marked deleted... when 
packing the base, the nondeleted headers are copied to the new file and the 
message bodies that match are copied to a new body file... pointers are 
adjusted as necessary...

much easier to acquire the MKSRCMSG package... its got all this stuff figured 
out and available already... there's even a sample program or two... one of 
them "converts" message bases between those available... BTW: those are *.MSG 
(SDM), HMB, SQU, JAM, and old(er) EZYcomm...

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

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

)\/(ark

 
* Origin: (1:3634/12)

.