Anyone use InfoPath?

I'm working on a little project at work updating a software support list. Basically I need to ask about a dozen people what version of the software is currently being supported, who makes it, where it's running, etc. There are a few hundred software titles being supported so rather then send out e-mails and update by hand I figured this would be a perfect time to try out InfoPath.

InfoPath seems to be very generic in the sense that I can't just generate individual forms with data I already have and the data binding seemed pretty useless. Since I already know the software titles and I have the old information, I'd like to generate all the forms individually so they could see what information was already known and update it accordingly.

In my short experience I couldn't find a way to do this and it seems that this mentality doesn't work well with InfoPath. Anyone have any suggestions?

Here's a short example. I already have this data:
Software Title: Program A
Version: 1.0
Comments: Upgraded on 3/22

I want to generate a form with the following:
Software Title: Program A (read only text box)
Version: 1.0_______
Comments: This product is no longer supported____
(Submit)

Which they would then submit.

Thanks

An infopath document is just an xml document with some extra processing instructions to bind the document to a particular form and to tell the os it's an infopath document rather than regular xml. 

If you create your form and fill out a sample document, you should be able to examine the resulting xml and figure out a way to generate your documents without using infopath to do it.  Once the documents are generated, you can send them out to the users who will be able to modify them in infopath.

Andy914's right - TimP you can design your form and then save an example of it and then look at the XML. You'll then see where the text goes for the title, version, and comments. I don't know where your original data is coming from, but it's just a few scripts away from turning those into %1, %2, %3 fields to be printed one by one into individual XML files.

If your data is in a database that InfoPath can hook up into, though, I'd say go that route because then you can have they users query for a particular title, update, and save back into the DB.

One big hint in the design of your form: perhaps you want to take all of these responses and merge them into a single document? If so, make sure you design your form so that the title, version, and comments is a repeating structure (you can add more than one, even if you're just editing one at a time) so that you have that merge opportunity in the future. Given the merge, you can even go and easily export / import that into another application for analysis, reporting.

Give it a test run! I'm certainly interested in hearing how it goes.

Eric