On Tue, Sep 13, 2011 at 2:35 AM, IVP wrote: >> Could I list them separately though? >> >> data 0xXX, 0xXX, 0xXX, 0xXX > > If you do it that way they'll be in order, but in consecutive words > > =A0org 0x4000 > > =A0data 0x01,0x02,0x03,0x04 > > 4000 0001 > 4002 0002 > 4004 0003 > 4006 0004 Which means every second TBLRD* is 0x00. Not great. I guess I could multiply by two, but that seems to be getting overly complicated just to make the source look clean. > =A0data 0x0102,0x0304 > > 4000 0102 > 4002 0304 Ok, but if I read this using sequential table reads, I'd get (in sequence): 0x02, 0x01, 0x04, 0x03, correct? To answer Jan-Erik's questions, I'm trying to find a way to put a lot of data in my source without it getting too visually hard to follow. All the while trying to make sure that it's easy to read programmatically. I find it non intuitive when looking at the data block defined in the code to have to remember to flip every second byte. That said, having every second byte stored as a zero in the actual memory isn't great either. I thought that there was some combination of db and code_pack that made this work, but I'm just as confused about it as I was before. I'm going to do some playing around and hopefully I'll figure it out! Josh --=20 A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. =A0 =A0 =A0 =A0 -Douglas Adams --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .