Hi Neil,

thanks for the feedback. I found a blog where a guy was complaining about limitations of it: http://weblogs.asp.net/dburke/archive/2004/02/16/73578.aspx but I guess this could have been the pre SP1 version. What do you think of his comments? I am tempted to just do the thing in VFP automating Word and Outlook or .NET if they insist on having a browser based interface.

My understanding is that the forms filled in (using InfoPath) just create XML files which are then sent back and forth between users and Infopath opens the XML on each user's PC. IS this correct? I guess then I'll need to store the XML files in some back end database as well?

Thanks,

>Frank,
>
>InfoPath is a great product for form processing and it has been made a lot better with SP1. The automation model is a bit lacking - we use it a lot in conjunction with web services from SharePoint. The following simple example will open an InfoPath form for editing (fill out form) using the automation model.
>

>goTest = CreateObject("InfoPath.Application")
>? goTest.XDocuments.NewFromSolution(getfile("*.xsn"))
>

>The next version (12) will have an InfoPath server and will allow you to embed forms into web pages and .NET WinForms.
>
>http://channel9.msdn.com/Showpost.aspx?postid=127821
>
>In my opinion a tool like InfoPath has been long overdue in the Office suite.
>
>Regards
>Neil