Are you populating the date by script? Or is this a date the user is selecting? Here's what I see when I set it up.I add the field to a blank document and set the display pattern as described previously.I preview the document and select a date.The date looks like the fomat that was requested.

This should do it.

You may need to modify this a little to suit your purposes: It doesn't catch list items with a blank space.var lbList = xfa.resolveNode("lbStuff.#items"); for (i = lbStuff.length-1; i>=0; i--){ if (lbList.nodes.item(i).value == "") lbStuff.deleteItem(i);} I tested with a list box "lbStuff" that con...

if (HasValue(DOB1) and HasValue(retireDate1)) then  var retireDate1_ = Date2Num(retireDate1.formattedValue, "MM/DD/YYYY") var DOB1_ = Date2Num(DOB1.formattedValue, "MM/DD/YYYY") var diff = retireDate1_ - DOB1_ var years = Floor(diff / 365.25) var months = Floor(((diff / 365.25) - Floor(diff / 3...

Also, I used your script and set the event language to formCalc. It works just fine to get the years. I think there's just some coding logic + math required to get the leftover bits from what floor rounded off and multiply by 1200 (or something).

Can the other two fields be changed to date fields instead of date/time?What error are you getting with your current script?

I was able to make this work with Age1 as a text field. Of course, you can do whatever you want with it, but this method made the most sense to me since I can say "99 years 99 months". If you need to separate the year and month into different fields, you should be able to do so easily. Lastly, this ...

Where does your content area start? That's where any content added to a new page will begin. Check the master page that you're using, and make sure that the header isn't covered by the content area.

Can you provide your script that you're using? Are you limiting the keystrokes in the script or in the object settings, or are you limiting to the visible area? The reason I ask is that this script limits the number of keystrokes, and forces the focus to the next field so that the final keystroke is...

Not sure exactly how you have the rest of the page set up for your needs, but here's what I did.Two buttons: btnAdd and btnRemoveOne Fragment: sfIssueAction: When btnAdd is clicked, add another instance of sfIssue.sfIssue:Object > Subform. Allow Page Breaks within Content is not checked (You should ...