How about setting that field set to currency with currency set to zero decimals? Unless you need real currency fields with the normal number of decimals in which case maybe change the real currency to double and be careful!!
Regards, Alastair. ----- Original Message ----- From: "Bill Downall" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, June 28, 2004 7:52 PM Subject: [RBG7-L] - RE: [RBASE-L] - Re: ODBC Data ..MORE INFO > Bob, > > NUMERIC (19,0)??? Wow, that's a big, big integer. > 99,999,999,999,999,999 > > In R:Base, NUMERIC can only go up to 15 digits of precision. In fact, even DOUBLE > is limited to 15 digits of precision. Curiously, the data type that can hold 19 or more is > CURRENCY. (I think it has something to do with the size of the national debt when > Republicans are in office. Is the federal budget being done with Pervasive SQL? Uh- > oh, Bob, the former Bush budget director is running for Governor of our fair state!) > > I'm not sure what you can do with an ODBC connection to a data type that looks > illegal from the R:Base point of view. Perhaps this is a place where the SSQL > command can work. Form the Pervasive syntax correctly, and pass it directly to the > P-SQL system with SSQL > > Bill. > > > On 28 Jun 2004 at 12:42, Thompson Technology Consultants wrote: > > > Razzak or others... > > > > Any other ideas on a solution for the datatype issue I am having? > > > > Again, I need to make updates to a Pervasive database (part of an > > accounting package) and the SATTACH command reports that there is an > > unsupported datatype. (It is a numeric,19,0) > > > > Thanks for any assistance! >
