Missing OnClose event

[Sven Steinacker]

Hi,

InfoPath allows to programmatically intercepting the loading process
by catching the XDocument::OnLoad event. I'm lacking the complementing
event XDocument::OnClose event that would be fired if the form is
closed regardless if changes have taken place or not.

This would allow for implementing a standard check-out/check-in work
flow needed if access to the form shall be granted to one user at a
time only: When the form is opened via a hyperlink to a standard web
server, the server locks the form for any further access. This lock
would have to be release in the moment the user closes this form in
InfoPath. I do not see a way to implement this behavior without
XDocument::OnClose.

To release the lock via the OnSubmit event is, of course, no good idea
as it does not work in the case the user does not change anything or
do multiple submits (the latter could be avoided by letting the form
close after a submit).

Anybody who stumbled over this problem before? Any alternative
approach appreciated (as long a it does not suggest to buy an MS
SharePoint Services, which is not an option in our particular
scenario).


BR
Sven Steinacker, Ericsson

 

[Brian Teutsch [MSFT]]

You can close a form after doing a submit in SP1. I understand there's still
some need for an OnClose event, but would that solve your problem?

Brian

 

[Sven Steinacker]

Not really, as it does not cover the case a user changes nothing and
simply closes the form. Also in this case the server lock would have
to be released. I cannot force the user to do a submit nor can I
forbid a close.

Sven

 

[Matthew Blain \(Serriform\)]

Brian:
Does InfoPath call HTTP LOCK on any WebDAV sever, or only on SharePoint
servers?

--Matthew Blain
http://tips.serriform.com/

Not really, as it does not cover the case a user changes nothing and
simply closes the form. Also in this case the server lock would have
to be released. I cannot force the user to do a submit nor can I
forbid a close.

Sven


"Brian Teutsch [MSFT]" <[email protected]> wrote in message

You can close a form after doing a submit in SP1. I understand there's still
some need for an OnClose event, but would that solve your problem?

Brian

 

[Brian Teutsch [MSFT]]

Don't know Matt, don't know. It's possible that InfoPath doesn't do it for
either, and that some code on SharePoint locks the file in given situations.

Brian

Brian:
Does InfoPath call HTTP LOCK on any WebDAV sever, or only on SharePoint
servers?

--Matthew Blain
http://tips.serriform.com/

Not really, as it does not cover the case a user changes nothing and
simply closes the form. Also in this case the server lock would have
to be released. I cannot force the user to do a submit nor can I
forbid a close.

Sven


"Brian Teutsch [MSFT]" <[email protected]> wrote in message

You can close a form after doing a submit in SP1. I understand there's still
some need for an OnClose event, but would that solve your problem?

Brian

Hi,

InfoPath allows to programmatically intercepting the loading process
by catching the XDocument::OnLoad event. I'm lacking the
complementing
event XDocument::OnClose event that would be fired if the form is
closed regardless if changes have taken place or not.

This would allow for implementing a standard check-out/check-in work
flow needed if access to the form shall be granted to one user at a
time only: When the form is opened via a hyperlink to a standard web
server, the server locks the form for any further access. This lock
would have to be release in the moment the user closes this form in
InfoPath. I do not see a way to implement this behavior without
XDocument::OnClose.

To release the lock via the OnSubmit event is, of course, no good
idea
as it does not work in the case the user does not change anything or
do multiple submits (the latter could be avoided by letting the form
close after a submit).

Anybody who stumbled over this problem before? Any alternative
approach appreciated (as long a it does not suggest to buy an MS
SharePoint Services, which is not an option in our particular
scenario).


BR
Sven Steinacker, Ericsson