Jump to content


Click the link below to see the new game I'm developing!


Photo
- - - - -

legacy version of proiv upgrade to access

convert files from proiv

4 replies to this topic

#1 Donald Rossoll

Donald Rossoll

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Lexington, United States

Posted 15 December 2018 - 09:20 PM

I have an older customer that is running version 2.0 of proiv and I need to copy date from that file system to some sort of flat file.  The file definition in proiv has a SEQ field that I don't have any documentation about, but it seems like if I could use that, I could convert my data easily.  I have over 26000 records to convert.  Thanks



#2 Neil Barber

Neil Barber

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:Milton Keynes, United Kingdom

Posted 15 December 2018 - 11:58 PM

Hi Donald

How many source (PRO-ISAM) files do you need to convert and what's the source system, DOS/WIndows, Unix, VMS or mainframe?

You're right in identifying 'SEQ' as a target file type that'll allow you to create an externally organised file that's ASCII encoded, but the source data will still have to be transformed.

The most expedient way is to use a Report function, one for each source file. Include each of the source file's fields in the Report Field Definition. Suppress Headers/Footers. Set the Spooler Options as the physical file you want to write the data to. The output will be sequential. Each field will be fixed width.

If there are a lot of fields in the source file, or a lot of source files, or you require the values tab or comma separated, let me know, I have a Java toolkit that can take care of it.


Regards



#3 Neil Barber

Neil Barber

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:Milton Keynes, United Kingdom

Posted 16 December 2018 - 12:45 AM

Hi again Donald

I negated to mention using the 'SEQ' method. Sorry.

To do so, make a copy of the source Logical File Definition, set that target's File Type as 'SEQ', define its Alternate (the physical file) name and assign its fields a Storage Format, then write an Update function that reads (using 'L'ook mode) the source and writes (using 'B'oth mode) the target.

The advantage of the first method is that it does allow you to insert a literal (delimiter) between fields in the Report Field Definition, notwithstanding those fields being fixed width, but that's a bit more portable. It also means just one additional object and no chance of polluting the Data Dictionary.


Regards


Edited by Neil Barber, 16 December 2018 - 12:46 AM.


#4 Donald Rossoll

Donald Rossoll

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Lexington, United States

Posted 17 December 2018 - 05:42 PM

Milton,

I just got back from my customer's location and after several mistakes on my part, I was successful in converting the customer file to a sequential file that I can now convert and read it into access.  Thank you for your help and I want you to know I really appreciate it.  Thank you so much.

Don



#5 Donald Rossoll

Donald Rossoll

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Lexington, United States

Posted 18 December 2018 - 03:32 PM

Milton,

I was successful in creating an SEQ file from proiv but it has 29 separate fields and I am having trouble getting them into access.  You mentioned you had a java toolkit that would work for me and that might be just what I need.  I'm not real familiar with java, but would you let me know how I can obtain this toolkit I would certainly appreciate it.  Thank you again for your help.

Don

drossoll@twc.com





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Click the link below to see the new game I'm developing!