AccPac has some limited export/import capability, but as I am needing to update only certain fields of existing data, I would be forced to do a mass delete before importing the modified records back in. I am VERY cautious about doing this as AccPac has some VERY odd table links and field characteristics. (Such as using a Numeric field type for dates and this numeric 19,0 for a unique record identifier) Since I cannot use the PROJECT command, these tables having over 100 fields each, would require a lot of time just to create matching tables. (One really gets spoiled with SQL and Rbase for sure!)
While this may be a possibility, I am leaving it for the very last resort! Thanks, -Bob > When all else fails, can the db you're attaching to send out data in an > ASCII file, XLS file, etc? > > David Blocker > [EMAIL PROTECTED] > 781-784-1919 > Fax: 781-784-1860 > Cell: 339-206-0261 > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, June 28, 2004 2:20 PM > Subject: [RBG7-L] - RE: [RBASE-L] - Re: ODBC Data ..MORE INFO > > > > Larry, > > > > Thank you for the suggestion. I gave it a try, but results are the same. > > The table will attach, listing all fields except the ones I need! > (Numeric,19,0) > > The sad part is, these fields have no reason to be such a high precisoin > number! > > > > I even tried to set the ALIAS columns to "numeric,19,0". Rbase actually > allowed me to set the fields as such! Rbase did report an error, (value > must be between 1 and 15) but the 19,0 values did "keep" and even showed > 19,0 in the LIST TAB command. However, the SATTACH still reported an > unsupported datatype. > > > > R>list test > > > > Table: TEST No Lock(s) > > Descr: TEST TABLE > > > > No. Column Name Attributes > > --- ------------------ -------------------------------------------------- > ---- > > 1 AORDUNIQ Type : NUMERIC (19, 0) > > 2 DISCBASE Type : DOUBLE > > 3 DISCAMT Type : DOUBLE > > 4 DUEBASE Type : DOUBLE > > 5 aDUEAMT Type : DOUBLE > > Current number of rows: 1 > > > > Unless I can get this to work, it looks like we may have several thousand > manual entries to make, so any more ideas is greatly appreciated! > > > > Thanks again! > > -Bob > > > > > > > > Any other ideas on a solution for the datatype issue > > > > I am having? > > > > > > You might try that aliasing technique, coercing the > > > NUMERIC 19 fields to TEXT. Sometimes databases use > > > straight text storage for those very high precision > > > numbers (and efficiency be damned!). > > > -- > > > Larry > > > > > > > >
