Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We use Infopath at work, quite frequently for form design and then we integrate this into MOSS 2007.
What I don’t yet know is what advantages are there to designing a form in Infopath as opposed to making a webpage (eg ASP.NET/C#) to allow for the same intention?
Thanks
I’ve only used InfoPath for one or two things in MOSS. It seems to me that InfoPath is a bit more integrated into MOSS than trying to use .Net webforms from a data retrieval/modification standpoint. That being said, virtually everything we have been doing in SharePoint lately that isn’t easily done in a webpart has been done through .Net webforms.
From a flexibility standpoint I think you have more options with the .Net framework then what you get in InfoPath, especially if we have to use multiple form that interact with one another almost like an embedded SharePoint webapp.