Re: [OzMOSS] SPSiteDataQuery and Calendar recurrence

2008-10-05 Thread Sharepoint Consultant
The Problem with this approach is I need to query across the entire site collection based on contenttype. Accessing each Calendar individually and querying the data would not be very efficient. That is why I would have liked to use SPSiteDataQuery. I am very, very aware of all the reasons for not a

RE: [OzMOSS] SPSiteDataQuery and Calendar recurrence

2008-10-05 Thread Dave Porter
Is this a Pilot or POC? If it is a Production system, do not go the Direct Database Route, it is not supported and if you mess up something...then well...there you go. I wouldn't advise it. Try these to see if they help... http://sridharu.blogspot.com/2008/01/how-to-read-recurring-events-using

Re: [OzMOSS] SPSiteDataQuery and Calendar recurrence

2008-10-05 Thread Sharepoint Consultant
As bad as it is, perhaps the most efficient way is going to be directly accessing the Database. I know it is never a good idea to do so... but we are left with very little choice on this one. Any more thoughts? On Fri, Oct 3, 2008 at 8:57 PM, Bill Williamson <[EMAIL PROTECTED]> wrote: > Recurra

RE: [SPAM] RE: [OzMOSS] Document Information Panel and Custom Fields

2008-10-05 Thread Dave Porter
The entire office integration platform, utilizing VSTO. It's all dev centric. You can use InfoPath to create/edit the DIP, with little or no code and have the ability for dev stuff later. It is much easier to make calls with the built in InfoPath controls (User, Membership, Roles, etc...) and re

RE: [SPAM] RE: [OzMOSS] Document Information Panel and Custom Fields

2008-10-05 Thread Paul Culmsee
As in asp.net code behind? Why would it behave differently whether in a browser or a browser that's embedded within the DIP? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Porter Sent: Sunday, 5 October 2008 8:41 PM To: listserver@ozmoss.com Subject: [SPAM] RE: [OzMOSS] Do

RE: [OzMOSS] Document Information Panel and Custom Fields

2008-10-05 Thread Dave Porter
Two words...Code Behindthat's why. From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: [OzMOSS] Document Information Panel and Custom FieldsDate: Sun, 5 Oct 2008 19:59:31 +0800 I always wondered why Microsoft didn’t consider using embedded IE for the DIP rather than infopath. Taking zones an

RE: [OzMOSS] Document Information Panel and Custom Fields

2008-10-05 Thread Paul Culmsee
I always wondered why Microsoft didn't consider using embedded IE for the DIP rather than infopath. Taking zones and all that sort of crap out of the equation, would have meant the DIP should work with custom fields. This tends to be a showstopper for many of the 3rd part solutions that are gre