Import Data from Advanced Revelation To Microsoft Access 97 (AREV Specific)
At 01 DEC 1998 12:11:54PM Kalpana Rajan wrote:
I would like to know how I can import data from Advanced Revelation to Microsoft Access97.
At 01 DEC 1998 01:03PM Jay Fox wrote:
There are many ways to do it, but the simplest would be to use RLIST to export the data to a text file, and then to import the text file into Access.
More specifically, use PDISK to redirect printer output to a file. Use SET-LPTR to set the page length to a number which is longer than the number of data records (this will avoid annoying page breaks and headers in the output file). Use LIST (and the dictionary for the AREV file that contains the data you are interested in) to select and/or sort the records and format the output listing and send it to the printer (ie, file). Finally use PDISK PRN to close the text file.
At 01 DEC 1998 01:51PM Richard Wilson wrote:
You can use the export functionality of Arev to a Dbase file
and the import that same dbf file into access
At 01 DEC 1998 04:35PM Capt'n Kirk wrote:
Re-directing output to a disk file works fine but has two inherant problems.
1. Data formating will be fixed width and importing may be more work than desired.
2. Fields with oconv of T#?? or multivalues will wrap to multiple lines.
What I have done is to perform the LIST statement using the (SX) option to produce Rbasic code (DOS record RLIST is created) and then modify and compile that code. I modify the output to trim the data and place a delimiter between fields for easier importing.
Capt'n Kirk
At 02 DEC 1998 01:36AM Curt Putnam wrote:
The dBeast approach is a lot easier
At 08 DEC 1998 06:33AM Larry Wilson tardis@earthlink.net wrote:
Actually,if you take a little time to analyze your data and figure out how to ASCII export it (with conversions for the IDs to make them compatible and the other items also; ie. dates), then exporting to ASCII and building a SCHEMA.INI file works the best and assures accurate import. Additionally, if you then upsize, it's a no pain plan.