Re: Weird situation with a customer's SQL INDEX

On 8/27/13 7:37 AM, CRPence wrote:

An SQL INDEX without a member is an effectively /unsupported/
condition, yet is not a fully prevented condition; i.e. the database
allows and can effect the no-members condition in some non-SQL actions,
but there may be side effects due to the expectations, i.e. some coded
assumptions, that every [non-partitioned] SQL INDEX has its one member.

Hmm. Would whatever caused the index to not have a member also cause it to return the aforementioned large negative number as its join spec array displacement in QDBRTVFD?

Is there any way that transferring it from one box to another might have caused this mangled condition?

I mentioned that (based on its filename) it appears to be either a JDE World file, or an E1 file, and based on its apparent SQL origins, and lack of column headings or field text, it is most likely the latter. Could that have anything to do with it?

--
JHHL