Hi, Use FormCalc (not JavaScript). I think you have a "total" field for each week (i.e. total and Monday are siblings?). If so//////////////////////////////////////////////////////////////////////     if   (Activity == "Holiday")then          $ = Sum(Monday, Tuesday, Wednesday, Thursday, Friday)    ...

Hi,Just to make sure you understand and there is no confusion, make sure you are using Jono's advice for using FormCalc instead of JavaScript. I find FormCalc is much more forgiving navigating the SOM and has really nice built in functions for date calculations. So, Jono is giving excellent advice. ...

Hi,Need more information. On what field and what event are you placing your script? $ in doesn't work in JavaScript (use "this")If you are placing the script on a dropdown box, on the Change event, "this" returns the previous value, not the current valueif Monday[i].value is referencing a SOM objec...

Hi,What you describe sounds like "invisible" instead of "hidden". Invisible objects still occupy space--hidden objects don't any occupy space. Be sure to use "hidden" to get the results you want. In addition, What I believe what you need is to use a Flowed container (with hight set to expand) and a ...

Hi, now I get it.OK, I hate to tell you this, but you should know--it can be done with 128 instances of 1 page, instead of 128 pages. You could create a cover sheet with input parameters, like a field that you enter how many cards and a button to produce them--now you're up to 2 pages total.I don't ...

I may not understand your problem completely. If you want all pages to have access to the same set of 5 random numbers, then use "variables" (that are global in scope--don't confuse this with setting field binding to global). You create "variables" (lets name them:  var1,var2, var3, var4, var5) in t...

Try setting it up as a script object--turn it into a function.

OK let me preface this with--I could easily be wrong about this: So take the following with a grain of salt:In XFA,  an attribute is actually a sibling of the child elements in the SOM hiearchy--your experience seems to bear that out. I tried manually adding a custom attribute to the XML in Designer...

Hi,You haven't explained how you currently hide the button. The way I would handle it is to use the preSubmit event with the following script on the button.this.presence = "hidden";      //javascriptor $.presence = "hidden"       //formCalcGood luck!Stephen

I'm not sure in your business organization, if this is possible or allowed by your IT. On my business PC, I would do a "repair" install of Designer and Acrobat.  But, of course, I set the rules here.