InfoPath Dev

I've developed an information panel that uses a multi-selection list box to populate a lookup-column in a SharePoint document library.  It works great until I try to use it against the 'Project Documents' library that comes with the  'Microsoft Office Project Workspace' template---when I try to use it there, the checkboxes are disabled and cannot be checked or unchecked.

The weird thing is that I *can* make selections using the default SharePoint upload/tag/check-in web page!  I can upload, tag, and save, say, a Word document, and then when I open it in Word, the correct list items are checked in the list box and everything---I just can't uncheck them (or check others)!

As an additional clue, the info panel also uses a multi-line textbox tied to the standard Keywords tag column---this textbox is enabled in the info panel, it's just the list boxes that aren't.

Can anyone explain what's going on, and how I can get around it?

Thanks,

  Joel

Hi Joel and welcome!

What is "Information Panel"? Is this an InfoPath web part application? Are you using InfoPath Form Services? What version of MOSS do you have? Need some more details.

Hi, Patrick---thanks for your response.

No, an information panel's not a web part, it's an infopath form incorporated into an Office application for the purpose of collecting poperty/tag information on a file.  Here's some info on them:

http://office.microsoft.com/en-us/infopath/HA102019671033.aspx
http://msdn.microsoft.com/en-us/library/ms550037.aspx

And no, not using Form Services.

MOSS, Office, and InfoPath versions are all 2007.

Thanks,

  Joel 

Hi Joel,

Oh, yeah, that thing! Sorry, but we don't do much with it. My guess is that it's a schema limitation of the project library but that's just a guess.

Patrick,

I was thinking that it might be a schema thing too---what messes with me though is that my custom tag fields are supported by the automatic SharePoint interface (i.e. - when I use the SharePoint 'upload' mechanism (with the automatic asp tagging interface), instead of saving directly from Word (with the Infopath panel), it works fine).  It makes me wonder if there's something wrong with the schema just in my Infopath file, but I'm new to Infopath and don't really know how to sort it out.  The schema is automatically generated when I initially create the Infopath form and tell it to base the template on the SharePoint content type.

 Joel