Razzak, Thank you for your reply and assistance, it is great to have this type of support!
I followed your suggestion, but did not have success. I am pasting the screen below in case I have not followed the steps properly. R>SDETACH ALL NOCHECK R>LIST TAB TEST Table: TEST No Lock(s) Descr: TEST TABLE No. Column Name Attributes --- ------------------ ------------------------------------------------------ 1 ORDUNIQ Type : DOUBLE 2 DISCBASE Type : DOUBLE 3 DISCAMT Type : DOUBLE 4 DUEBASE Type : DOUBLE 5 DUEAMT Type : DOUBLE Current number of rows: 0 R>SATTACH OETERMO <WARNING> Unsupported datatype for column ORDUNIQ in table OETERMO (2626) <WARNING> Unsupported datatype for column DISCBASE in table OETERMO (2626) <WARNING> Unsupported datatype for column DISCAMT in table OETERMO (2626) <WARNING> Unsupported datatype for column DUEBASE in table OETERMO (2626) <WARNING> Unsupported datatype for column DUEAMT in table OETERMO (2626) R>LIST TAB OETERMO Table: OETERMO No Lock(s) Descr: Server table - OETERMO HFINC No. Column Name Attributes --- ------------------ ------------------------------------------------------ 1 PAYMENT Type : INTEGER QualKey 2 AUDTDATE Type : NUMERIC ( 9, 0) QualKey 3 AUDTTIME Type : NUMERIC ( 9, 0) QualKey 4 AUDTUSER Type : TEXT 8 QualKey 5 AUDTORG Type : TEXT 6 QualKey 6 DISCDATE Type : NUMERIC ( 9, 0) QualKey 7 DISCPER Type : NUMERIC ( 9, 5) QualKey 8 DUEDATE Type : NUMERIC ( 9, 0) QualKey 9 DUEPER Type : NUMERIC ( 9, 5) QualKey Current number of rows: SERVER When browsing the SATTACHED OETERMO table, I do not have access to the "DOBULE Data type" fields. They are not included in the table. (For instance, ORDUNIQ is the first field in the Pervasive table, but as seen above, it is skipped and PAYMENT is #1) None of the Double datatype fields are included. Any thoughts or suggestions would be greatly appreciated! Thanks again, -Bob > At 01:07 PM 6/24/2004 +0000, Bob Thompson wrote: > > >I have some more info on the "unsupported data type" mentioned on the > >below attached thread. > > > >I was mistaken when I stated I could not attach to the "Decimal" data type > >fields. Looking more closely, I can attached to some, but not others. The > >difference between the decimal type fields that I can link to and the > >decimal type fields I cannot link to, is the precision listed in the > >Pervasive database. > > > >These fields are linking to Rbase as NUMERIC type fields, which default with > >a (9 precision,0 scale) The Pervasive data base fields that are not linking > >show values of 19 for precision and 0 for scale. The HELP context states > >that Rbase defaults to 9 , but supports 1-15. Since 19 is not in the range > >supported, it is erroring out. > > > >Is there anyway to attach to these columns as I need to update data in an > >urgent situation? > > > Bob, > > Here is one way: > > 01. Start R:BASE 6.5++ (Build: 1.866xRT03 or higher) for Windows > > 02. CONNECT dbname > > 03. SDETACH ALL NOCHECK -- to detach any sattached table(s) > > 04. Create a dummy table in R:BASE with exactly the same column name(s) > (as in Pervasive database) but having the data type as DOUBLE in > R:BASE table. > > 05. Now SATTACH those tables from SCONNected data source and see what > happens. > > The same technique applies when using R:BASE 7.x for Windows! > > Hope that helps! > > Very Best R:egards, > > Razzak. >
