I had a directory on a separate server where I would archive records each year. I performed the SET LOCATION from AREV and every time I needed to view these records I would simply attach the archive location. The network people decided to move the data to another server. The files or tables are still there but when I attach the new location AREV can't "see" the older tables. How can I attach these tables or "fool" AREV into seeing these again? Any help will be appreciated.
Thanks
Check your Volume Identifier to see if it uses a SERVER_ID. If it does, you can edit it to point to the new server name. You will have to be logged into that server before you start AREV. If the Volume Identifer points to a Drive Letter, then you will have to log into the correct server and map the location to the same drive letter before you start AREV.
Don Miller
C3 Inc.
Don,
Thanks for your answer. Where do I find the Volume Identifier? Is this a table or a record in a table? Is it only accessible from SYSPROG?
John
John
On the app menu choose DBAdmin, Location then pull up the volume identifier (as per Don's suggestion)
You can also EDIT SYSVOLUMES VOLNAME where VOLNAME is the arev volume identifier.
Tony
Tony,
I can get to EDIT SYSVOLUMES VOLNAME and I see the tables that are listed on the volume. When I try and add the names of the older tables and save it, I get the message that SYSVOLUMES is a "Read Only" file. I checked the attributes and they don't indicate "Read Only". Can system files be edited?
John
John ..
Did you ever get this resolved??
Don Miller