I have the same experiences as you.  I do the tabbing order as the very last thing before publishing the form to use on our repositories. I just want it to take less time and I do not want the system to fight me on it.  I wish they had a way so you could turn off the system driven tabbing order and ...

I start with the automatic tabbing but it doesnt always suit the design of the form.  So, it needs manual alteration and you can manual change something only to have it screw up the tabbing on the rest of the page and pages you have already done.  Another bad part about the automatic is when you hit...

9.0.0.2. is the version I am using right now.  It did get better with previous versions but it still seems to have a lot of bugs and it wants to fight you every step of the way.

Okay, I did as you instructed and the additional part of the expression is added but I still receive the same error.  Do I need to delete the first line of the code or does this supplement it?

Could it have anything to do with the fields being inside a table?  I took the numerical fields out and the calculation worked fine.

Unfortunately, I cannot.  I work for a financial services company and the form has not been approved by the SEC yet so I cannot post it anywhere.Are you looking for this:  form1.#subform[15].#area[7].Table3[3].Row1.empIncome::calculate - (FormCalc, client)

The one I am having the accessor error is "Sum (empIncome, investIncome, pensionSSN, otherSource)"  The accessor error is showing up for the first one, empIncome.The one I am having an issue with sum showing up is "Sum (bondsAmt, certofDep, commoditiesAmt, exchangeTraded, fixedAnnuity, marginTrading...

I guess another question I have is to see if there is anyway to test within Livecycle that the data is actually being encoded on the form.

Now, I read that you need to Livecycle Barcoded Forms to make use of this feature.  Do you know if this is something that comes seperately or does it come with ES2 SP2?

Works great!  Thanks.