third_party_content:community:commentary:forums_nonworks:a25ed7c9b39e49c085256bd00056e14b

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 06 JUN 2002 11:48:57AM T Henderson wrote:

Greetings, all. I've got a question after a few attempts at my first ASCII import in AREV 3.x. I've got a db of contacts (records contain typical fields, i.e. first/last name, address, city, etc.), and I'm trying to add a txt file w/ about 500 records to the existing table. I'd like to put the new records in no particular order in the table; there are some blank keys throughout the table from old records, and it's fine to use those key numbers. The problem I'm having is that the new imported data will only write to the FRONT of the table (i.e. the first 500 key numbers), even though I've chosen the option of appending the new data. Also have chosen the option of merging data with the existing table. The documentation is not very clear on this, and I wonder if others have had experience w/ this process.

Thanks, –Tim


At 06 JUN 2002 05:52PM Jonathan Bird wrote:

I think you are better to "roll your own" import routine. You end up with more control and know whats going on. I could let you have an example routine, if you like.

[email protected]


At 07 JUN 2002 05:05AM Hippo wrote:

I have no experience with it, I always program it my own way, but if the problem is only with the @IDs, there is an easy method:

Import it to a free table (just for this purpose) and copy (using RBasic) the @RECORDs whenever you want with whichever @IDs you want.


At 07 JUN 2002 10:15AM T Henderson wrote:

Jonathan, that would be useful, if you have one you could e-mail or post here. Thanks, –Tim

[email protected]


At 08 JUN 2002 03:58AM Warren wrote:

The source for IMPORT.ASCII should be included on the Utilities/Options disk in a self-extracting archive REVSRC.EXE.

You can easily modify it to suit your needs. Look at the source for IMPORT to see how to pass parameters to IMPORT.ASCII. Then you can write your own stub to call your modified routine (and thus keep the stock RTI version in place).

This way you can continue to use the IMPORTEXPORT table to define the major parameters and not have to reinvent the well or worry about the data structure of IMPORTEXPORT.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/a25ed7c9b39e49c085256bd00056e14b.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1