Bob,

After the project try sdetaching the original source table. You should then be 
able to alter the projected temp table as your requirements dictate.

Ken

----- Original Message -----
From: [email protected]
Date: Thursday, May 20, 2010 6:01 pm
Subject: [RBASE-L] - Project table from ODBC table
To: [email protected] (RBASE-L Mailing List)

> 
> 
> Anyone have any ideas about the below.  The projected table has 
> a column data type 
> 
> issue on the column name ORDUNIQE 
> 
> 
> 
> 
> 
> --Column is defined in other tables as shown below.. 
> 
> 
> R>list col orduniqe 
>  Column Name        Table Name         Attributes 
>  ------------------ ------------------ --------------------------
> ------------- 
>  ORDUNIQE           OEORDH             Type   : BIGNUM  (19, 0) 
> QualKey 
>                                                                  
> Comment: #ORDUNIQ 
>                                  OEORDHO          Type   : 
> BIGNUM  (19, 0) QualKey 
>                                                                  
> Comment: #ORDUNIQ 
>                                  ORDEROPTIONAL      Type   : 
> BIGNUM  (19, 0) QualKey 
>                                                                  
> Comment: #ORDUNIQ 
>                                   tmpDiscount        Type   : 
> BIGNUM  (19, 0) 
> 
> 
> 
> I now project a temp table from an ODBC table 
> 
> 
> 
> R>proj temp tmporders from orderoptional using all where 
> compdate = 0 and Optfield = 'FRTCOST' 
>  Successful project operation, 926 rows generated. 
> 
> 
> 
> However, the projected table has the incorrect data t ype for 
> column ORDUNIQE 
> 
> 
> 
> R>list col orduniqe 
>  Column Name        Table Name         Attributes 
>  ------------------ ------------------ --------------------------
> ------------- 
>  ORDUNIQE           OEORDH             Type   : BIGNUM  (19, 0) 
> QualKey 
>                                                                
> Comment: #ORDUNIQ 
>                                  OEORDHO          Type   : 
> BIGNUM  (19, 0) QualKey 
>                                                                
> Comment: #ORDUNIQ 
>                                  ORDEROPTIONAL      Type   : 
> BIGNUM  (19, 0) QualKey 
>                                                               
>  Comment: #ORDUNIQ 
>               *********      tmporders           Type   : 
> BIGNUM  (38, 0)   ******** 
>                                   tmpDiscount        Type   : 
> BIGNUM  (19, 0) 
> 
> 
> 
> The original ODBC table has the same data type and size as all 
> other tables. 
> 
> 
> 
> R>list table OrderOptional 
> 
>    Table: ORDEROPTIONAL        No Lock(s) 
>    Descr: Server table - ORDEROPTIONAL HFINC 
> 
>  No. Column Name        Attributes 
>  --- ------------------ -----------------------------------------
> ------------- 
>    1 ORDUNIQe           Type   : BIGNUM  (19, 0) QualKey 
>                                  Comment: #ORDUNIQ 
>    2 ORDNUMBER          Type   : TEXT 22 QualKey 
>    3 COMPDATE           Type   : NUMERIC ( 9, 0) QualKey 
>    4 ORDTOTAL           Type   : CURRENCY QualKey 
>    5 OPTFIELD           Type   : TEXT 12 QualKey 
>    6 VALUE              Type   : TEXT 60 QualKey 
>    Current number of rows:   SERVER 
> 
> 
> 
> 
> 
> Any thoughts?   The two issues is that #1, the BigNum size does 
> not match and 
> 
> more importantly, I need to issue an ALTER TABLE command on the 
> PROJECTED 
> 
> table tmporders.  The command fails as it returns an error 
> stating that ORDUNIQe 
> 
> is used in another table and its type cannot be redefined. 
> 
> 
> 
> version V8. 
> 
> 
> 
> -Bob 
> 
> 
> 

Reply via email to