In AREV32 I have had a lot of difficulty moving an app. For example, my OI is installed in C:\revsoft and my source tables are in C:\revsoft\FDINV. The volume name was created by an attach to be FDINV. When I copied the app to M:\revsoft\FDINV I got an error on the attach saying "\FDINV is not a valid volume name". To get the app to allow the attach I had to put the tables in M:\FDINV which has given me occasional "Invalid Volume" errors.

Is it best to create volume names before attaching tables?

Thanks, Jim

Is c:\revsoft your root folder where oinsight.exe is located? If so, when the tables are properly attached the pathing should be relative instead of absolute.

If your root directory is c:\revsoft and your data was stored in c:\revsoft\FDINV then you should be able to just attach "FDINV" instead of "C:\Revsoft\FDINV".

What does the OpenInsight database manager show, absolute or relative paths?

Just to clarify, did you move or copy the system? If you copied, is it possible that C:\RevSoft\FDINV still exists and is automatically getting attached? When you try and attach M:\RevSoft\FDINV the volume names would clash because the REVMEDIA volume name is identical between both folders. This only applies if you copied the system OR have the same volume name already attached.

Hi Jared

Yes, OI engine is in c:\revsoft. The system was originally built in c:\FDINV for development purposes. I copied it to my local M:\revsoft\FDINV to prepare for deployment on the Client's server's M:\revsoft, which is where his OI is located. I was advised to put the app in a folder under the OI.exe folder to get the relative mapping and the ability to copy it so I copied it to C:\revsoft. that is when I got the arrors on attach that "FDINV is not a valid volume" so, to get it running I copied it back to C:\FDINV and now I am having indexing problems and messages about invalid volumes.

I know this is a mess. Can I solve it by:

1. Deleting the FDINV app from the OI in C:\revsoft,

2. adding a new FDINV app in C:\revsoft (where my OI.exe is)

3. Specifying the new volume FDINV pointing to C:\revsoft\FDINV before copying or attaching any tables,

4. remove all indexes from my source tables

5. Using COPY_TABLE to move the tables to C:\revsoft\FDINV

6. Add the tables to the app

7. re-do all the indexes.

Or can I change volume pointers using the System Volume Pointers dialog?

Thanks,

Jim

View this thread on the Works forum...