InfoPath Dev

I'm wondering what problems might arise when I change the defined namespace to another?

<xsd:anyAttribute processContents="lax" namespace="http://www.w3.org/XML/1998/namespace"/>

This would help me in resolving an issue I have with unknown attributes.

Hi Toetankh,
We typically use xsd:any elements and not attributes. However, I believe that InfoPath should have no trouble since it supports xsi:nil and other attributes without too much trouble. Extract your solution and modify the xsd and see what happens.

Patrick,

Thanks for your reply. My issue was related to another thread I opened about namespaces. This is the solution I'm using currently:

It seems that I've found a solution to my issue. Now is the time to verify whether what i've done is a good idea. Please comment....

I extracted the form files
I opened myschema.xsd
Then I changed this (under the root element):

<xsd:anyAttribute processContents="lax" namespace="http://www.w3.org/XML/1998/namespacehttp://www.documentum.com"/>

seems that you can add a whitespace seperated list of namespaces?

I also used any/other, but thought this was the safest solution.

Regards,

Sven