Ok then,
If your lookup table is a short one (less than 250 lines approx) then you can load the value into pclath within the same sub where the lookup table is situated (and this is good practice esp if the routine can be called from more than one place in the software), in my example you can see the label 'table', I load up pclath straight after the software calls 'table'.
You can count the lines of assembler to work out exactly where the table starts in the pics memory, I cant be bothered and just write the software and use a dummy value to load into pclath (2 in my example), then assemble the code, then open the .lst file that the assembler generates (you might have to enable the list file generator on your assembler) and look at the page the table is situated in, I think the first or second column of the .lst file is the address in hex, the third and fourth least significant bits are the page number, 00 page zero, 01 page 1, 10 page 2 etc, then just go back and edit the dummy value with the actual page number.
You can if your lazy put the lookup table right at the start of the code listing to guarrantee that the lookup table is within page zero, because pclath resets to zero you can then just forget all about pclath and write the code as per normal.
All this only applies to absolute code.