-
As per #1 above:
Although InfoPath uses HTML to render the views, it is heavily sandboxed and many of the features that would work in a web page will not work in InfoPath. This is a security feature and will likely not be changed.
-
Hi. I've never done anything with LDAP before... that one is outside my knowledge range. Hopefully someone else will be able to answer that one for you.
-
Open your XML file in a text editor and see if it starts with the following processing-instructions:
<?xml version=''1.0'' encoding=''UTF-8''?>
<?mso-infoPathSolution name=''{NAME HERE}'' href=''{HREF HERE}'' solutionVersion=''{VERSION HERE}'' productVersion=''{INFOPATH VERSION HERE}'' PIVersion=''1.0.0.0'' ?>
<?mso-application ...
-
I've been running that combination of products for the last several years with no issues.
What kinds of issues are you experiencing?
-
Thanks for sharing this. Glad to have provided some help in the right direction.
-
Glad to have helped. Good luck with your project.
-
Set up your main connection to only pull the data you want to eventually submit, then set up secondary connections to your database to pull the remainder of the data. You might need to use a master-detail control to show all the data from the secondary connection that is readonly info.
The other option (sorry, requires coding) is to have a Web ...
-
Are you positive that current() is pointing to a value that should match with @Access_record, and that it shouldn't perhaps be something more like 'current()/@attribute' or 'current()/Element' or something?
-
You are encountering a bug I've described (along with a workaround) here: Bringing Expressions Out of the Box
-
Great! Glad you got it working!