Let me start by saying I know absolutely nothing about Arev. I am trying to export some tables out of an old system which doesn't have Export as an option but I have found a back way in.

So far I have been successful in exporting (in ASCII) the look up tables but am having trouble exporting the main storage tables. I can get to the "Export ASCII" window but after I fill in the information, select my table and its fields & then press F9, I am receiving a message that says "Entity" (or in some cases "Location") is not in the dictionary. These are not fields in the tables & I have know idea what a dictionary is. It then boots me out to the TCL window.

It didn't do this for the look-up tables, only the main storage ones.

Is there an easy remedy to this? Something that you don't need alot (or any, for that matter) of Arev to understand?

Thanks all

Exports can be remarkably simply and frustrating at the same time.

Start with trying to do a Listdict filename at TCL. If you can do that then note whether or not there are multi-valued fields. If there are multi-valued fields, you will need to figure out whether they need to ne normalized or not - and how.

If you can't do a listdict then you have another problem.

Try and report back.

I have a Rev/Arev to ASCII routine for free if you wnat to try it. Many users of this Discussion group have requested a copy and have been pleased with its capabilities and ease of use.

Many non-Rev users have found it easier to use than the standard export utility. However, it will export complete files only. A registered version is available that will output specified fields only and output multi-values as separate records.

Email me on: [email protected] for a copy.

I was able to do a listdict & it showed me my fields but I have no idea what a multi-valued field is or what to do from this point.

I inherited this system & I've never used Arev before, so the simpler the better.

thanks

Multi-values are AREV's version of repeating values in flat file records. They can be broken out into relational data records, but you have to have a solid understanding of the data you have and the data you want to end up with. In my limited AREV experience it is not uncommon to horrible messes in OPADs (other people's AREV databases), because AREV is so flexible that some people are undisciplined in their data designs.

I can give general help on multivalue stuff, but am unfamiliar with Jocelyn's and other utilities.

[email protected]

View this thread on the forum...