1. As users felt the length of FPATTADAR field is short, we increased it to 70 characteres. 2. The Pattadar Serial No. & Group No. were taken care of. This is not a astructural change, however, but worth mentioning here. Since the Serial & Group no. were independent of each-other, we accepted a suggession by an operator (Ranjan Sarmah): We mendatorily use six(6) digit PAT-ID field, where the first three(3) digits depict the Group No. and the rest three(3) digits are used for Pattadar Serial No. which is a no. starting from 001. E.g., Thus, 001001 = Pattadar 1, belongs to Group 1 001002 = Pattadar 2, belongs to Group 1 002003 = Pattadar 3, belongs to Group 2 003004 = Pattadar 4, belongs to Group 3 004005 = Pattadar 5, belongs to Group 4 and so on User can use the NEW_ID field just below the PAT_ID field of the Pattadar screen of the lrc.frm to modify an existing PAT_ID. (See lrc.hlp for details) Now, if there are rows in asjp1 with PAT-ID whose length is four(4) digits instead of six(6) digits, it would create trouble. So, please run (after compiling) the pat_id.pc routine to convert any such short PAT_IDs into six(6) digit ones. 3. In some districts, extra remarks(part of dags owned by a Pattadar Group) exist against Pattadar Groups in the Pattadar column of Jamabandi. We have come to the following decisions after discussion with H.K.Saikia, PSA & co-ord, Trg Div.: a) That these extra remarks were not mendatory entries, rather redundant entries. b) That though in some pattas, the there was no remarks entry, but only these aforesaid extra remarks in the pattadar column. c) Therefore, We modified the ORACLE system as detailed below: A new table GRP_LND is created with following structure- create table grp_lnd ( VLCODE VARCHAR2(11), PAT_TYPE VARCHAR2(4), NEW_PAT VARCHAR2(12), grp_id number(3), grpshare_dags varchar2(70), grpshare_b number(6), grpshare_k number(3), grpshare_l NUMBER(2), primary key ( vlcode,pat_type,new_pat,grp_id)); The BLOCK pattadar of form lrc is modified to incorporate the last four (4) fields. As it is clear from the structure, the table inserts a new row only when the GROUP id changes (not when the SERIAL code of the PAT ID). Now, the GRPSHARE_DAGS field would store the dags for a group separated by commas, and the SUM of land areas for these dags would be then inserted into the next 3 numenric fields for Bigha, Katha & Lessa. Thus, we are incorporating these redundant remarks in a limited & simplified manner. d) In case of no Remarks as in point no. b) above, we instructed the operators to shift these aforesaid extra remarks from the pattadar column to corresponding remarks column. We will shortly take-up the matter with Commissioner, Revenue.