InfoPath Dev

Hello,
A colleague raised a very good point today on WEBDAV within the SharePoint Forms library. So, in my solution I've created custom submit function on my form and locked down toolbar, and unnecessary functionality; I want the submit functionality on the form to be the only way to contribute to the form library. How do I stop people from using webdav in the library and copying in another form/document. Obviously, I can remove the webfolder view page (explorer view) from the library and modify the toolbar to stop uploads/creation of new folders. But, I can still create a my network place, and drag and drop other files into that library (with contributor rights). I don't want to disable webdav in IIS6 (total server) because other users use this functionality on other document libraries, and I cannot see an obvious way to disable webdav on a specific URL/folder. Has anyone got any ideas on how to stop webdav/drag and drop in the InfoPath forms library?
Thanks.

Hi Craig,
Cool question and very relevant. Surprised this hasn't come up before. I think adding an event handler to SharePoint is one possible solution but will require code and server install. Another possibility is to use a Web service to save the forms and restrict user permissions on the form library, but then you lose some functionality. I wonder if Microsoft is going to address this in O12.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Good point Patrick, on the O12 enhancements. I wonder now that this has been raised it might open up some holes in any existing SharePoint integrated solutions out there.

I ran into a similar (but different ;^) issue. I want people to contribute, but not be able to read submitted forms. I could have read-only permissions or read and contribute permissions, but it doesn't seem like SharePoint could give contribute but not read.

I also needed to restrict the submitters on a form-by-form basis.

This was solved with a separate FormSubmitService that processes submitted InfoPath forms. It checks the submitter's role against Active Directory, does schema validation on the submission, updates a reporting database (where users view the data according to a separate security model using Reporting Services), and then PUTs the form to SharePoint using a separate system account.

Worked for me, anyway.

Regards,
Mike Sharp