You searched for the word(s): 12
-
InfoPath 2010 has cached your old XSN and refuses to update automatically.
Please force InfoPath to obtain the update. Steps are detailed here:
http://www.infopathdev.com/blogs/ernesto/archive/2010/08/13/infopath-2010-fails-to-update-dat-due-to-caching-issue.aspx
-
I managed to find the screenshot you e-mailed, but I need a picture of your data source, like this one:
you can attach images by clicking the Options tab when you're replying to this thread.
-
Thanks for the info.
Searching on Google for the error I've found the following ...
-
hi
to fix my previous problem "http://www.infopathdev.com/forums/t/18068.aspx" i downloaded and installed the new software from your special link given to by patrick and mel.
now i get this error which i have attached .
i have tried some suggestions from here ...
-
Hello,
Would you mind providing a more complete description of the scenario and the issue? You can use the Options tab when replying to attach an XSN or attach screenshots. I don't understand your description above. Sorry!
Thank you.
-
Glad to hear you downloaded some of the accelerators.
We don't make much money from the accelerators (and none from this site which costs us a lot every year). We're here to help you bridge the InfoPath gaps. Let us know id you need help. We're here to make you shine.
:)
-
Well, I'm not sure why your friend recommended a web part in place of a Web Service. Seems they don't have any clue about InfoPath solutions architecture ...
Anyway, you can download Qdabra's free trial. It's easy to install and set up and it's inexpensive and a best practice since it's the only "data-driven" Web ...
-
Hi everyone,
I have some templates prepared in InfoPath 2007, where I have used customised commands to add, remove insert before and insert after section. I used a form toolbar to show them in convenient way to the users.Now some users are using InfoPath 2010 and this toolbar with commands has gone.
After some investigation I found that in ...
-
I'm pretty sure this is not a datatype issue. Hence the term "non-data type errors" :-)
-
The cause of this error usually is, if you are trying to update a field having a certain datatype with values that does not match that datatype, for eg. if you are trying to enter a string value to datetime control, you can do that but in that case you have to frmat the control to use string values.
I would need ur infopath form and code ...