Config Collate Alternate
Posted: Tue May 22, 2012 3:04 pm
Hi Everyone,
During our daily indexing the following commands are issued:
EXECUTE 'config collate alternate'
index statement 1...
index statement 2...
etc....
EXECUTE 'config collate native'
I'm wondering what the config collate alternate does differently. I am in the process of migrating from 4.16 to 4.18 and anytime I come across an index file that is processed after the config alternate command I get an error 0632 which is Problem with index file. I'm tempted to just take out the config collate alternate statement and see what happens but I'm sure there must be some reasoning as to why this type of indexing was used. I wasn't able to turn up any info about it on the Wiki.
During our daily indexing the following commands are issued:
EXECUTE 'config collate alternate'
index statement 1...
index statement 2...
etc....
EXECUTE 'config collate native'
I'm wondering what the config collate alternate does differently. I am in the process of migrating from 4.16 to 4.18 and anytime I come across an index file that is processed after the config alternate command I get an error 0632 which is Problem with index file. I'm tempted to just take out the config collate alternate statement and see what happens but I'm sure there must be some reasoning as to why this type of indexing was used. I wasn't able to turn up any info about it on the Wiki.