Can UDC's be created through WSS 3.0? (NOT MOSS)

I am currently working in a WSS 3.0 farm environment that incorporates Forms Server...

I have been developing a set of Web-enabled InfoPath Forms with managed code and have hit the cross-hop domain issue...

I have code behind a button that dynamically calls Data Connection(s) through web service(s) and I have NO issues if the form is run through the InfoPath client...

On the SharePoint server running InfoPath Forms Services, when I try to trigger the above code, I get the Log ID: 5337 message but cannot locate ANY messages in the event log...

The bizarre thing is ALL other local code in the form(s) work and FIXED data connections bound to controls work as well!

What are my options here:

> Apply a code-signed certificate to ALL forms?
> Use an Anonymous/Service Account for SharePoint?
> Use Kerberos Authentication?

I believe with WSS 3.0 I cannot build a connections library so that means I cannot create  Universal Data Connections (UDCs)... is that a correct assumption?

I am EXTREMELY frustrated with this... can ANYONE help please?  
chelseablueAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
chelseablueConnect With a Mentor Author Commented:
I have RESOLVED this myself...

The managed code issue was a combination of two things:

> The application of a code-signed certificate to the form(s)

> Also I had an issue of setting the values to XML Nodes with blank values... applying the following code to EACH related field/control resolved the issue...

 public void DeleteNil(XPathNavigator node)

{

if (node.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))

      node.DeleteSelf();

}
0
 
Andres PeralesCommented:
I think for this to work also you need to have SSO, WSS does not support SSO that is supported by MOSS.  Have you tried uploading the data connection to a normal document library and just try it that way?
0
 
chelseablueAuthor Commented:
Thank you for the quick response...

SSO is not a solution I am afraid...

Applying a code-signing certificate HAS helped and at least I have isolated another problem null values from this... I will post some code relating to this tomorrow as I dont know the workaround yet...
0
All Courses

From novice to tech pro — start learning today.