Thank you for the reply. The issue isn't the syntax of the xml file.
That is fine. What was happening is that characters such as accent
symbols (grave and acute instead of single quote) were in the source
text for the field itself. I was able to resolve this by replacing many
of the characters before they were added to the XML file and using a
different type of encoding - ISO-8859-1, instead of UTF-8.
I have designed a form where an externally created XML file is imported
into the form via xfa.host.importData(); This typically works great
except when there are certain special characters in the XML fields (&,
accent symbols, etc.). In this case, the form just goes blank. I've been
able to replace most of the special characters in the XML files, but
there are still some that I haven't been able to chase down. Is there a
way to do error trapping on this to be able to know where the problem is
Thanks for the suggestion. What I ended up doing is creating a
navigation page with it's own bookmark which contains a repeating
subform with a "Go" button and the name of each Section in a read only
Text Field. A new entry is added to this page each time the user creates
a new Section. The "Go" button uses setFocus to take the user to each
section - similar to a bookmark.
Thanks for the reply. Do you know of any other method where the user
could navigate to these other than scrolling through. Each instance can
be multiple pages and there can be 40 or more instances. That's the
issue I'm facing.
Hello,I have a dynamic form with a repeating Section (Subform) called
Section 3. I've created a book mark to the beginning of this Section
(1st Instance) by going into the XML Source tab and adding an "extra"
tag as shown below. This works great and the bookmark always goes the
beginning of the section regardless of how much the form expands and how
many new Section 3s are added. However, I would like to dynamically add
a bookmark each time the user adds an instance that would link to the
Thanks for the reply. I could do that, but it would require two separate
forms and an extra step of creating the XML file. Also, the form will
work in the opposite direction. Some information will be pre-populated
in the form and then distributed to the user to fill the rest of it out.
It would be quite a bit easier to just have the folks that fill it out
understand that they just need to okay through that message, but that's
not an ideal solution. It may not be possible, but being able to
I have a form where most of the users will simply fill out the form and
send it to a central location where the form gets reviewed and then
submitted to a database through ODBC data connections. The problem is
that the users that fill the form out don't have and don't need the
database that the form connects to. So, when they open the form, the
form will not be able to find the ODBC connection the data connection
refers to and they get the "connect operation failed..." message.Is
there a way to ...