There are so many levels of symbolic reference indirection going on in this snippet, that I am surprised that the compiler can keep track of them, let alone you.

I know I certainly cannot.

With 90% of the variable names in the program being constructed from contents of other variables. And the contents of those being constructed from others, who's content is read in from a combination of bits from any number (unknowable) of files, your problem could be anywhere.

A duplication of a word at any point in the hierarchy of files that is used to derive your variable names and you will be overwriting one label with another, or one set of labels with another, or entire frames, one with another.

There is simply no way for us, or you to know. Without the contents of the files this program is entirely unreadable.

And as the contents of the files can be changed, you, nor anyone else can never know whether this program will ever be correct.

If I ever saw this program work. I would shut down the system involved, and make a back-up copy of all the files that contribute to the naming of the variables in it, onto a CD.

Because running the entire system from read-only media, is the only way that will be able to guarentee that the program will ever run correctly again.

Oh. And please make a second copy of the CD for me. I'll pay for the shipping. That would be like having a picture of a blue moon, a meteor falling to earth, or finding an Archaeopteryx fossil.

Good luck! (You may find these 1. 2, 3 references useful).