In my experience, using the object model is limited to the same Farm (as
suggested by many others). The web services provided by SharePoint are
reasonably powerful, and I don't really see any reason not to make use
of them in your scenario.
However, I'll give you the best tip I've come across when using the
Lists web service: the return value is a messy collection of XML nodes,
use the following to extract only the data nodes:
XmlNode returnValue = listsService.GetListItems("<your
list>", null, query, viewFields, null, queryOptions, null);
String xpq = "//*[local-name() = 'data' and namespace-uri()
= 'urn:schemas-microsoft-com:rowset']/*[local-name() = 'row' and
namespace-uri() = '#RowsetSchema']";
XmlNodeList listItems = returnValue.SelectNodes( xpq );
I found this on Paul Ballard's blog
(http://weblogs.asp.net/paulballard/archive/2005/05/08/Using-Data-From-S
harePoint-2003-Lists.aspx
<http://weblogs.asp.net/paulballard/archive/2005/05/08/Using-Data-From-S
harePoint-2003-Lists.aspx> ), and using the XPath query defined above
makes life so much easier - trust me. :)
Hope this helps,
David.
This is an email from Fujitsu Australia Limited, ABN 19 001 011 427. It is
confidential to the ordinary user of the email address to which it was
addressed and may contain copyright and/or legally privileged information. No
one else may read, print, store, copy or forward all or any of it or its
attachments. If you receive this email in error, please return to sender. Thank
you.
If you do not wish to receive commercial email messages from Fujitsu Australia
Limited, please email [EMAIL PROTECTED]
------------------------------------------------------------------- OzMOSS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com
