Please switch on debug mode by adding the following line to your config.php file:
$debug = '1';

Are there any additional errors reported?

Can you add a screenshot?

Today I had the first chance in several days to look at this work and problem. This is why I have not yet responded to Mazi's suggestion.

I went into my survey, and I again tried to build conditions for an item, and it worked fine. I repeated with several different items in different configurations to see if it continued to function properly, and it seems to work.

So what could have caused to not function is my question now. The circumstance was quite real, which leads to the thinking that the context in which the problem occurred might be the problem. The following is my description of the context and suggestion for what might be happening:

The computer I experienced the problem with was a laptop at work. The configuration is a 2.5GB RAM Dell with an Intel Core Duo CPU. I was running a lot of applications and had a number of windows open while working on this project. The survey is fairly complex, with a 48/17 question items/groups configuration. I have turned on the assessment features, which are being used with most of the question items. I have designed 14 assessment rules.

I'm thinking that with the complexity of the survey together with all the other open windows that when I was using the condition editor, it was not pulling down the item result possibilities from the label sets I am using - so this is possibly a RAM issue.

On Monday when I get back to work, I will try using the condition editor without the open applications and windows to see if the editor functions normally or not and add another note here with what I find.

The issue seems to originate from a configuration of Firefox on my PC at work, but I have not yet been able to determine exactly is the cause.

I have verified that the problem with setting conditions is still a problem, but only with Firefox (latest version) on that PC. Running the same version of Firefox at home, I do not have this issue. Also, this problem is not existent with IE or Chrome on the PC at work which has the problem.

I will continue trying to find what setting is creating the problem and pass it on to this group. In the meantime, I will set the issue to resolved.

-George