InfoPath Dev

Hello, any insight on the following is greatly appreciated...

Situation:

If "User A" accesses a previously submitted Form and "User B" tries to access the same Form, "User B" will recieve the following message:

"The form cannot be filled out because you do not have adequate permission, another user has the form open, or the form is open in another program. Do you want to open a read-only copy of the form?"

Question:

Does anyone know how I can display to "User B" the UserName of "User A" who has the form currently open?  I'm desperate in finding a solution to this as my end users are frustrated with this problem!

 Thank You!

Tom Barrett

There may be a way programatically to query SharePoint to see who has the document open - but I don't know if SharePoint keeps that information.  It would be a custom dialog though to get this to work I think.  In other words there is no easy way to do this in InfoPath that I know of

However, If you require that users check out a document in order to edit the document you may be able to do this - one of the coulumns that SharePoint returns is Checked_Out_To.  This would also show in SharePoint so the user could see who has the document open or checked out.  That solution may not be perfect though because users will forget to check something back in at times.

You could have person B try to check out the form.  Person B would get an error saying the form can not be checked out because 'John Doe' already has it open.  This error occurs even if person John Doe didn't check out the form, he just need to have it open.  Not as good of a solution as having an error box automatically pop up with the name of the person in the form.  But it at least gets you the name in a round about way!

Hope this helps.

The 'Check-in / Check-out" option won't work as the user recieves a customized SharePoint Designer eMail via Workflow that has the link back the document that requires their review / signature.  They just access the Form Submission via the url and interface that way...However, thanks for the thoughts...

Regards,

Thomas N. Barrett

Hi Thomas,

This post might be of help: http://www.infopathdev.com/forums/p/5922/22095.aspx.

Cheers!

I've been trying to find a solution too, for the original post of this thread. This article throws some insights on SPFile.SPCheckOutStatus.ShortTerm property, which may have one of many keys, to unlock this issue. But, that is beyond my reach. I am sharing it here hoping that someone solves it or that it gets included in qRules.