InfoPath Dev

The error message I get is

"An error occurred in the form's rules or code.
The number of rule actions or the number of calls to the OnAfterChange event for a single update in the data exceeded the maximum limit.
The rules or code may be causing an infinite loop.
To prevent this, ensure that the rule action or event handler does not update the data which causes the same rule action or event handler to execute."

I am using MS Access  from MS Office Enterprise 2007.

Please help

Hi,

Some where in the code you are setting a value or doing some thing in the on after change event which is calling infinite times (May be you are setting the a value in that field's on after change). Once verify that.

Thanks for the reply Swathip. 

I have deleted all the print view forms, and all the controls off the main Form. Yet the error still occurs!!!!!

I thought the problem was caused by an area I was working in.

But I have changed that area. Then deleted the changes .

And still the error occurs.

 So I am at a loss.

Please help.

I am thinking the code is buries somewhere. 

I don't use any code, I rely on the controls as is.
Apart fromn formulae in the controls.

On some situations, I have changed the database, and all the code in the controls gets cleared.
That also is a mystery.

 Ian

Please check the rules that you have on your fields.  The error suggests that a rule is setting the value of a field, which is again causing a rule to set the value of the same field, ad infinitum.  You may need to add a condition to the rule to stop it from reevaluating endlessly.

Thanks for the reply Jimmy.

Again, if I have an InfoPath file which contains a master form and two print view forms.

I added about a dozen rules to one control.
I thought that was the error.
So I created new Access fields and added them into the control, transferred all the of the rules out of the large control into separate controls.

I deleted the large control. And the error persisted.  I know all about looping etc, from many years of programming.

I noticed a checkbox to terminate processing for the control once the rule is processed. I clicked on that checkbox for many of the Rules in the one control
Now that should not cause a problem, Should it?

Anyay, as I stated in replies above, I deleted the 2 print views. Then tested the IP file. Still the error. I then removed most of the controls from the master Form.

Still the error. m The only controls left are key entry controls and buttons.
All of which have been working for months, and are left untouched at this point.

So it is still a mystery?

Maybe I should start from scratch and rebuild the whole file again (master form and 2 print view forms).

Jimmy I am looking forward to your reply, or anyone else available.

Ian.

Jimmy thanks for your reply earlier. Your reply was on the ball. As much as I didn't believe it.

It is nice to see some support people, try to help hewbies get a handle on how to solve problems. Unlike others who criticise my eff

The problem, I recently suffered, was soo simple it is funny, NOT. 

I had a 2 rules with 2 joining conditions. And the system error was generated because both rules had used "or" to link their conditions.

The error went away when I changed one "or" to "and". 

How simple was that!!!!!

ALL I can say is, the error message  "Infinite loop" was not very helpful at all.  I.E.  Not user friendly, I think you would say.

In Retrospect, and for everyone out there in the InfoPathDev world.  

If you didn't already know this, well know you should be aware of this now.
If you get an infinite loop message, chances are you have a condition error.

What I have trouble getting my mind over is, HOW DO YOU HANDLE else scenarios??????

Likewise, if condition 1  and condition  2 and condition 3   action.

But    if you want condition1 and (condition 2 or condition 3),  how do you handle that????????

Ian

Ian, the error was clear, and the replies were also clear.  It was an infinite loop caused by a rule, and rules are not bound to CONTROLS, but rather to data fields (same goes for data validation).

You can handle else statements with multiple conditions.  You can do 1 and (2 or 3) with the proper ordering of condition rules or by doubling the statement (1 and 2 or 1 and 3)