Hello,
I want to consult you for one problem. I've got Arev application with data volume WW (for example this volume has path C:\ONE\WW, and application's path is C:\ONE). I copied the same application into another directory C:\TWO so new copy of WW volume lays into C:\TWO\WW.
Both of these application work correctly. (Default data location is WW for both applications.)
Now I start Application_1 and want to access any table from Application_2. Inside Application_1 I described location WW_2 with DOS path C:\TWO\WW. When I try to ATTACHTABLE WW_2 I receive next message - "The WW_2 volume has the same label '11 :33:22 08 feb 2000' as the WW volume and cannot be attached."
Have I any means to solve this problem? How can I change the volume name and would it help me?
I'll be very gratefull for all advise. Thank you.
Peter,
This problem arises because the volumes are copies of each other. It wouldn't happen if each copy was deployed individually. The volume label contains a date/time stamp.
You can get rid of the problem by editing the volume label. It's in the REVMEDIA table. But also a lot of other places if the volume's tables got indexes. Then there's a lot of editing to do.
Then it's better to use a program to change the label. Mike Ruane posted one such program here: . (The posted version was for Arev even if it was posted in the OpenInsight section of the discussion.) I've also seen an Arev version written by Mike Pope. I can get hold of that for you unless somebody says it's not free to use. I don't know if they're the same.
- Oystein -
With Arev 3.12 I just do a namevolume
It's not just a matter of changing the volume label as the volume label is used in the indexing controls.
The latest version of OI includes source & object code of a RENAME_VOLUME program, which is apparently a conversion of an earlier ARev program issued some years ago by Sprezzatura to its "Revmedia" tech newsletter subscribers. This program does all the necessary changes. I've used it on OI and it works very usefully.
You could convert it back to Arev - or speak very nicely to Sprezz!
Richard Guise
Tornado Property Systems Ltd.
Thank you Curt, Oysten and Richard.
I thought over this problem and your advice. For my particular task I decided to choose another means - I created new volume and moved into that volume all tables which I needed. So second application remained the same. Inside first application I added only one sentence into logon script - Attachtable New_Volume.
Peter.