InfoPath Dev

That makes sense that you couldn't add a field to a table that's bound to a list.  Anyway, I'm glad I could help!

Hi, on 2010 conditionnal formatting has merge with rules so select your button click on "Managed rules",  set a condition, and on rules types select formatting and disable or hide your control.

attaching a clearer screenshot of this error

 Hi, thanks for the quick reply!   Edit: I found the place i need to change the  coding language but it presents a new problem as I have some VB coding which I have to have. I can fix this if I can find a way to export my form to PDF written in c#. Here is the VB code I have to export to ...

Thanks Jimmy, Looks like I have to use a bit of both :) The reason for not using a field is that it gives me an error (Cannot store data correctly). I assume this is because the repeating table is bound to a list but this field is not. So when I run the form the value for the first item is calculated but the rest are not. So that's ...

 You still need to check that the data connections are not executing every time on form load. If they are, then that's the reason why the user is being prompted to authenticate.

Thans for your reply :) The checkboxes of the data connections are marked for store a copy of the data in the form template.... How do I set them up correctly?

 Hi again, I found a solution while accidentally I found the exact translation of the error message. The correct translation is: The assembly 'Example_published.dll' from form template 'Example.xsn' ('urn:schemas-microsoft-comffice:infopath:Example:-myXSD-2005-10-21T21-12-27') conflicts with a same named assembly in ...

Hi Guys, I'm new to InfoPath and I have a couple questions. The first one is about how to hide a section until a query has been made. I also want to make it so that the repeating section adds only one new record, and cannot be accidentally deleted by the user once they've created it.  Basically I've got an access database on ...

It sounds like your form still has some data connections that the outside user has no access to. You'll need to edit your data connections such that the data is stored in the form that gets saved locally, and set them up such that they don't execute when the outside user opens the form.