Topic:
Upgrade 10pX to GF3.5 produces duplicate field names. 

Description:
SYMPTOM:  Upgraded an IESX 10pX project to GeoFrame 3.1.4 or 3.5. 
          The upgrade produced duplicate field names and each field contained 
          a different number of wells.  
          This problem is caused by blanks in front of or behind field name
          in IESX that are different for the same field name.      

Solution:
WORKAROUND:  There are four different ways to fix the problem:

1.) Proman Backup/Restore will automatically combine duplicate 'like'
    fields into one.

2.) Use Data Save to save the well data to an archive file, delete wells in 
    General Data Manager, and reload archive well file with Data Load which will
    also combine duplicate 'like' fields into one.

3.) a.) Open 'Wells and Boreholes Data Manager' and select the boreholes  by
    clicking on 'Boreholes...' and click control/MB1 on the wells you want to
    move. 
    b.) Once wells are in 'Wells and Boreholes' list, select the 'Select rows'
    icon, second from the left, to highlight all wells if they are not already
    highlighted, then select the 'Display fields', icon nine from the left.
    c.) In the 'Select Fields' list, select the field to move the wells to.
    Click 'Ok'. Should see the selected field in the Field column. Then select
    'Apply' and 'Ok'.

4.) Use sql to combine 'like' fields into one.  It is recommended to have a
    current backup before proceeding.  Once these changes are made in Oracle,
    there is no way to undo the edits.  The example well field name in this
    case is called WC.

    a. Create field WC_orig in gfdm. (In General Data Manager, project 
       should be highlighted, select Edit/Create field)

    b. In sql, type
       >sqlplus projectname/projectpassword 

    c. Find the id no of this field; say it is 12345:
       sql>select id from field where name like 'WC%';

    d. Change the container of all wells contained by fields with
       name as WC*, from WC* to W_orig.  It is very important
       that the container_id number is correct.  To obtain this
       number(in the example 12345) find the field W_orig in
       the General Data Manager and use display format or attribtues
       menus to obtain the id number for that field.
   
       sql>update well set container_id = 12345 where id IN
          (select id from well where container_id IN
          (select id from field where name like 'WC%'));
      
    e. Save changes to oracle
       sql>commit;
   
    f. Exit and reopen GeoFrame
       At this point you should be selecting any of the fields with WC in
       it(except WC_orig) and when expanding the wells should show up under
       WC_orig)
   
    g. Run or type in script leo_1.sql (see below).
       To run script in sql:
       >sqlplus projectname/projectpassword
       sql>@leo_1.sql
       (Need to run sqplus in directory where sql files are located)

    h. Modify script leo_2.sql (see below) to modify the x.Descendant_id number
       to be the same as the container_id number used in step 3.

    i. Run script leo_2.sql (see step 7) 

    j. Commit to database
       sql> commit;

    k. Exit and reopen Geoframe
       Confirm that all fields with WC in it except WC_orig have no
       data children. Delete all these fields from General Data Manager.
    
<<>> 

DELETE FROM Containers WHERE Ancestor_Id IN 
 (SELECT Ancestor_Id FROM Containers WHERE Descendant_ID IN 
       (select id from well where container_id IN
         (select id from field where name like 'WC%'))
          and Distance != 0)
  AND Descendant_Id IN 
 (SELECT Descendant_Id FROM Containers WHERE Ancestor_Id IN 
  (select id from well where container_id IN
         (select id from field where name like 'WC%')));

<<>> 

INSERT INTO Containers 
(Ancestor_ID,Ancestor_Table,Descendant_Id,Descendant_Table,Distance)
SELECT x.Ancestor_Id, x.Ancestor_Table, y.Descendant_Id, y.Descendant_Table, 
x.DIstance + y.Distance +1 FROM Containers x, 
Containers y WHERE x.Descendant_Id = 17830754  and y.Ancestor_Id IN
(select id from well where container_id IN
         (select id from field where name like 'WC%')) ;



RESOLUTION:  Pending.  Nominated for GeoFrame3.6



Last Modified on: 08-APR-99