inconsistency, works, then doesn't work

[LanceK]

I have two files, one contains main topics, the second contains subtopics. I want to have a way to "check" them off when they are done, so I created a check field with one option, then made it so when that check field was checked an icon of a much prettier check is displayed (for printing purposes). Anyways I got it to work on the first file, then I wanted to do the exact some thing in the other file.... did it.... doesn't work!?!?

First file calulation(container) field formula:

Case(checkBox = " X", GetRepetition(gCheck, 1), GetRepetition(gCheck, 2))

Second file calulation(container) field formula:

Case(checkBox = " X", GetRepetition(gCheckTwo, 1), GetRepetition(gCheckTwo, 2))

arg... it should work... any ideas?

[dbruggmann]

If you created the whole field

[BobWeaver]

Also, make sure that gCheck is really defined as a global, and not a regular container field.

[LanceK]

Detlev, yep, both globals(BobW - it's a global container I double checked) in both files are filled in.

I tried it through a relationship before and ran into problems, so I said "no biggy, I'll just give it it's own", and that's were I am now.

I'm going to try it in some new files to see what happens.

[LanceK]

Well the new files worked, guess I'll just recreate it there.

It's still frustrating when you learn the rules, play by the rules, and then the rules are defenestrated.

[dbruggmann]

Yeah, and as usually the referee hasn't noticed anything

[-Queue-]

BTW, GetRepetition( field, 1 ) is redundant. field will work just fine. It's similar to the way a calculated repeating field assumes the current repetition and only needs specification if other repetitions are involved.