Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

ALIAS_TABLE USED FOR MULTIPLE TABLES (OpenInsight Specific)

At 17 OCT 2001 10:37:10AM Helen Furman wrote:

Hi Everyone, 

   I am working on a project that requires the ability to retrieve inventory data from a number of databases.  So far, I am just working in the command line of System Editor.  I issue two or more commands like the following:

RUN ALIAS_TABLE 'N:\XXDATA\T123\DB','ABC','INV_MASTER', 'INV_T123'

RUN ALIAS_TABLE 'N:\XXDATA\T987\DB','ABC','INV_MASTER', 'INV_T987'

If I do an 'Open Record', I can see that for each table, an index, dict and data file has been attached using the alias names. If I do an RLIST of the first table I alias, it returns the records, but, if I do an RLIST of the second table I get an error message, 'FS210 THE INDEX TABLE FOR "!INV_T987" IS NOT AVAILABLE.' I have tried aliasing the tables in the reverse order, and whichever table that I alias first is fine and the second gives the error message, so it is not the table that is causing the problem. Can anyone offer some help or suggestions?

Thanks,

Helen

At 17 OCT 2001 03:17PM Oystein Reigem wrote:

Helen,

Have the volumes perhaps got the same volume label?

- Oystein -

At 17 OCT 2001 04:32PM Helen Furman wrote:

No. That was the first problem I had, and the volumes I am using have all been renamed.

Helen

At 18 OCT 2001 04:02AM Oystein Reigem wrote:

Helen,

Here's what I have in my notes about this curious error message. (I assume you've noticed the message doesn't look quite healthy, talking about the index table of an index table):

FS 210. The index table for "!xxxxx" is not available.

Means the index table is not there but REVMEDIA still knows about it.

Or: No index but SI.MFS still exists in the REVMEDIA entry for the table.

- Oystein -

At 19 OCT 2001 05:15AM Oystein Reigem wrote:

Helen,

Don't know if that was of any help. But I think there must be some inconsistency in at least one of your volumes. Some confusion about indexes.

FWIW - I'm able to do what I think it is you try to do:

- I have an app with a database containing a table XXX.

- I have a couple of disk backups of that app lying around, containing earlier versions of XXX (i.e, older content).

- I change the volume label in the latter two versions so I'm free to alias their XXX tables from the main version.

- Then I successfully alias the XXX with alias XXX_2 from one of the disk backups.

- Then I successfully alias the XXX with alias XXX_3 from the other disk backup.

My table XXX has got Btree and Xref indexes, but not relational indexes.

- Oystein -

At 19 OCT 2001 08:49AM Helen Furman wrote:

Oystein, 

   When the volumes I am working with were renamed, the indexes were not removed first.  That is what was causing the problem.  Thank you so much for pointing me in the right direction.

Helen

At 19 OCT 2001 10:40AM Oystein Reigem wrote:

Helen,

So that's what it was. The last few years I've always used a RenameVolume program that can change the volume name while the indexes are present. So I forgot all about the problem.

- Oystein -

View this thread on the forum...