Jump to content

- - - - -

How to replace VIP codewhen importing

4 replies to this topic

#1 James



  • Members
  • Pip
  • 2 posts
  • Gender:Male

Posted 19 December 2005 - 07:54 PM


We're in the process of migrating our native ProIV code form Unix to the Windows version 5.5 with VIP. A while back we used the $XFR utility to import our functions to the Windows version for testing. I've been using this test code to get to know & learn VIP.

Here's the problem: We've made changes to the native code and want import it into the Windows version, overriding most (but not all) of our test functions. But when using the $XFR utility, it updates the native code, but not the VIP code.

For example, I've been playing around with a test function named "X" in VIP. When I use $XFR to import a new version of "X" into ProIV, the native code gets updated (I can see the code with @S, @SF, etc). But when I edit "X" with VIP, my test version is still there!

If I delete "X" before importing the new version I don't get this problem. But I have a list of several hundred functions, and don't think I should have to delete them all individually. Is there a solution to this problem?


#2 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 19 December 2005 - 08:29 PM


Not really. ProIV is not going to make any further changes to $XFR (according to our reps).

You may be able to get by on the cheap via the following:

1) Go into your directory
2) Back it up - because if this blows something up, I can't help you.
3) delete *.pro
4) isin vip.out

In theory, you now have a completely "pure" vip region. When you load your native and look at your functions in VIP again, they'll reload.



#3 Guest_Guest_*

  • Guests

Posted 19 December 2005 - 09:54 PM

VIP will import from a native export 'prx' file (as well as it's standard export 'vpx' format). Invoke VIP and go to the Tools tab (next to the system tab). Click on Import and then enter your file name. Then select the file extension type of 'prx' from the drop down list. Then click on Select All.

Be aware that only later version of VIP offer this import feature.

#4 James



  • Members
  • Pip
  • 2 posts
  • Gender:Male

Posted 19 December 2005 - 11:17 PM

Thanks for your responses. I decided to bite the bullet and delete the functions manually. It only took about half an hour to delete them and then reimport them.

Guest: I had looked at VIP's Import utility before, but overlooked the fact that it could import more than vpx files. I'm actually testing it out right now with a prx file, and one thing I'm noticing compared to $XFR: it's slow! It's been running for over an hour, whereas $XFR was finished with the same prx file in under 10 minutes. Oh well, it's nice to have alternatives.

#5 George Macken

George Macken

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 248 posts
  • Gender:Male
  • Location:Co. Wicklow, Ireland

Posted 20 December 2005 - 09:43 AM


if you need to re-do the process

you mention that on your Windows environment - you have functions that you want to keep and functions that you want to delete - set catg on those to be Deleted as OLD/JUNK - on the Windows environment - export those Categories that you want to keep, maybe this means an export of both the VIP and Native code (I dont use VIP)

then re-create the Windows account isin vip.out, load the unix .prx then load your windows exports

This may be quicker than deleting individual functions, I dont use VIP so cannot state that this is 100%, but I think would work.



Reply to this topic


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users