.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Licensing for InfoPath 2007 when using Rich Client Forms only

Posted By:      Posted Date: October 11, 2010    Points: 0   Category :SharePoint


I am using InfoPath 2007. I intend to design and distribute Rich Client forms only, and once the user fills the form, they will submit the data to a Web Service or Email the form data (xml). I am aware that each user will need to have InfoPath 2007 installed on their computer, which is ok for me. My question is, apart from purchasing the Office InfoPath 2007 (which in my case comes with Office 2007 Enterprise), are there any other licences I will need in order to deploy my solution?

Thanks and regards.

View Complete Post

More Related Resource Links

MOSS 2007 : I am looking for tutorial about how tu use infopath 2007 forms and to associate to them



I am quite new on sharepoint 2007,

i am at the moment looking for tutorial to help to understand better the concept of workflow you can associate with infopath 2007.

I would like to create a  form that the visitor of the website can fill and then submit.

once the form submitted i would like tto be able to store all the date picked up to the database sqlserver 2005 and then to be able to send a email to the administator to be kept inform  of that.

the 2 tutorial i found that i found interested are http://weblog.vb-tech.com/nick/archive/2007/02/25/2207.aspx and the microsoft one o.n the virtual lab.

So what i am looking for is any tutorial which can help me to be understand very well how to use the worklow with infopath or if you have as well some book to advice me for that i would be happy.


move infopath forms from SP Portal Server 2003 to 2007


I am a newbie to SharePoint. Please let me know if I didn't explain my problem well...

We built the new SharePoint server 2007 on a different physcial box from the old server 2003. There are huge amount of InfoPath forms in form library on the old server. I was told that: to get these forms moved over to the new server 2007, we have to save the forms and re-publish to the new server one at a time. This will be really time consume and also loosing the attributes of the original forms, the date it was created and modified etc.

I would like to see if there is a way to move one form library at a time, and just copy the forms over; not publishing them again.

Many thanks!


Moss 2007 and Infopath 2003 client


System config:

SharePoint 2007 SP2 - 64 bit Standard edition

2 WFE, 1 APP/index,  Clustered SQL DB Servers (SQL 2005)


Issues is with Infopath forms saved to a document library (NO FORMS SERVICES ENABLED - MOSS Standard license), no code behind, just XML based form with a number of fields in it linked to an xsn that is located on another server entirely.

Client machines are IE 6 Infopath 2003


When form is opened by an owner - works fine, client opens no issue

When form is opened by a contributor - unless checked out first or if the "Require checkout before allowing editing of file" is disabled works fine

When form is not checked out to contributor or if the user if a viewer the error is:

"Infopath cannot open the following file:<filename>.xml. The file does not appear to be an infopath form ."

Show details:

"The processing instruction in the file is missing or invalid"

I tried a couple tests, I logged into Windows as a user who had viewer rights and then logged into MOSS as a user who has owner rights. Issue still happens. So I am assuming there is a second call being made by the InfoPath client using the windows identity and integrated auth.

If I download the file to my desktop it opens just fine. I cannot determine what ch

calling InfoPath 2007 Client from SharePoint 2010 Foundation


I'm relatively new to SharePoint and very new to InfoPath. A client I just acquired hired me to develop a fairly complicated InfoPath solution that they want to be able to call from within SharePoint. Right now, they have a new SharePoint 2010 Foundation system and Form Server is not installed. They also currently have Office 2007, including the InfoPath client, on all computers in the workplace (this is an intranet only situation).

First, I created the needed lists/libraries in SP. Then I set to work developing the form in IP Designer 2010 (setting it for IP 2007 client compatibility). While the form is not yet done, I now want to setup a link in a ListView in SharePoint that launches the IP 2007 client on the user's computer, but I'm having troubles figuring out which way to go. There is a fair amount of C# code used by the form and while I'm an administrator on the server, I'm not familiar with setting up certificates to enable full trust (if that's what I need to do).

As a newbie, I'd really appreciate any pointers to existing answers or guidance of whatever sort.


Infopath 2007 form Submit error - Web client

I have set up a Infopath 2007 forms server
and published an Form that submits to a Web Service.
       On the same server, On a different port.

If I load the form in the InfoPath Desktop Client, the form submits just fine.

However, if i load via the web browser i get a "An error occurred while the form was being submitted."

Any Ideas?

how do i get more info on this error?
   There is nothing in the event viewer.


Programmatically submit Infopath Forms to the Sharepoint Library from client computer


Hello. I have a task to programmatically sumbit/update/delete infopath forms (from .NET console application) to Sharepoint server 2007. The application must work from client computers (without Sharepoint installed). Therefore I've decided to use Sharepoint web services (Lists.asmx), but after some time of investigation I've figured out that I can't work with Forms Library via Lists.asmx service. Please, advice me the most optimal solution. Some choices that I see:

- use some another web service to work with "Forms Library"

- use "List" (instead of "Forms Library") on Sharepoint (am I right, that I can submit/update/delete forms as file attachments? Am I right that this could be achieved with UpdateListItems/AddAttachment methods of Lists service?)

- implement a server and client applications to use Sharepoint Object Model on server side


Please, advice me the right solution. Thank you.

"Unbound rich text box not supported by InfoPath Forms Services"


I downloaded the Issue Tracking template from office.microsoft.com. I opened it in InfoPath 2010, changed the template type to "Web Browser Form" and validated it. It keeps throwing the error "Unbound rich text box not supported by InfoPath Forms Services."

There is a Rich Text Control on the form, but it's bound to an XHTML field. I deleted the control and dragged the node back to the form - same error. I create a new XHTML node in the data source and dragged *that* to the form - same error.

Any idea what's going on here?

Philo Janus, MCP Author: Pro InfoPath 2007 Pro PerformancePoint 2007 Pro SQL Server Analysis Services 2008 Building Integrated Business Intelligence Solutions with SQL Server 2008 R2 & Office 2010 Blog @ http://philo.typepad.com/with-all-due-respect/

Cutting Edge: Explore Rich Client Scripting With jQuery, Part 2


Achieving cross-browser compatibility for events is no easy task. The jQuery event handling API addresses the differences in event handling across browsers, allowing you to write more predictable JavaScript.

Dino Esposito

MSDN Magazine April 2009

Cutting Edge: Explore Rich Client Scripting With jQuery, Part 1


Thanks to selectors and function chaining, jQuery allows you to write compact, cross-browser code.

Dino Esposito

MSDN Magazine March 2009

InfoPath 2007: Designing Form Templates With The New Features Of InfoPath


InfoPath 2007 is an XML forms designer and editor, and a fully featured and integrated member of the Office family. This article takes a sneak peek at some of its new features.

Scott Roberts and Hagen Green

MSDN Magazine August 2006

Smart Clients: Craft A Rich UI For Your .NET App With Enhanced Windows Forms Support


The System.Windows.Forms namespace has increased by approximately 134 percent over the .NET Framework 1.1. There are 446 new public types; 113 existing types have been updated with new members and values; 218 types have been carried over from the original namespace. Read about it here.

Chris Sells and Michael Weinhardt

MSDN Magazine Visual Studio 2005 Guided Tour 2006

Draft a Rich UI: Ground Rules for Building Enhanced Windows Forms Support into Your .NET App


In this article, the winning Windows Forms duo of Chris Sells and Michael Weinhardt team up again to explore lots of new features and additions to Windows Forms 2.0 that will let you build more flexible, feature-rich controls, get better resource management, more powerful data-binding abilities, and make your development life a whole lot more fun.

Michael Weinhardt and Chris Sells

MSDN Magazine May 2005

.NET Framework 2.0: Craft a Rich UI for Your .NET App with Enhanced Windows Forms Support


The upcoming version of the .NET Framework offers a host of enhancements an order of magnitude over and above existing versions. In particular, developers writing Windows Forms benefit from a variety of new and improved features targeting development, deployment, increased productivity, and auto-generated code. This article covers some of the key new features including designer enhancements, new controls, data binding, and deployment to give you a taste of what's to come.

Michael Weinhardt and Chris Sells

MSDN Magazine May 2004

InfoPath: Turn User Input into XML with Custom Forms Using Office InfoPath 2003


Office InfoPath 2003 is a new Microsoft Office product that lets you design your own data collection forms that, when submitted, turn the user-entered data into XML for any XML-supporting process to use. With an InfoPath solution in place, you can convert all those commonly used paper forms into Microsoft Office-based forms and end the cycle of handwriting and reentering data into your systems. Today organizations are beginning to realize the value of the mountains of data they collect every day, how hard it is to access it, and are striving to mine it effectively. InfoPath will aid in the design of effective data collection systems. Here the author shows you how to get started.

Aaron Skonnard

MSDN Magazine September 2003

Visual Studio .NET: Building Windows Forms Controls and Components with Rich Design-Time Features, P


This is the second of two articles discussing the extremely rich design-time features of the .NET Framework. Part 1 discussed the basics, showing you where to start and how to extend your control implementation through attributes and interfaces, as well as their effects on the property browser, code serialization, and other controls. Part 2 continues the journey by concentrating on design-time functionality that you can implement beyond your components and controls, including TypeConverters, UITypeEditors, and Designers. It would be impossible to cover everything you can do in two short articles, which is a testament to just how all-encompassing and flexible the design-time capability of the .NET Framework is.

Michael Weinhardt and Chris Sells

MSDN Magazine May 2003

Visual Studio .NET: Building Windows Forms Controls and Components with Rich Design-Time Features


Visual Studio .NET provides support for designing rich features into your controls and components, allowing you to set properties, set form placement, inherit from base classes, and much more. So how does Visual Studio .NET do all this? What does the Windows Forms designer do? What's the difference between a control and a component? How does Visual Studio integrate your controls so that they can access features of the .NET Framework?In this article, the authors answer these common questions by building a clock control and taking the reader along for the ride. In building the control, hosts and containers are illustrated, the property browser is explained, debugging is discussed, and a general overview of the design-time infrastructure is presented.

Michael Weinhardt and Chris Sells

MSDN Magazine April 2003

Web-Aware Apps: Build Hyperlinks into Your Client App with the Windows Forms LinkLabel Control


LinkLabels are Windows Forms controls that enable a user to hyperlink to a URL that points to either the Web or the local directory system. While the SDK documentation discusses the control, it does not demonstrate how linking is accomplished, nor does it outline the power and flexibility the control provides. This article fills those gaps, showing how to link using the LinkLabel control. It also shows the flexibility of this control for the programmer using the .NET Framework. In addition, the author covers the large number of properties that allow you to customize your controls and accurately place them. Their built-in behaviors are also discussed, along with their use in both Visual Basic .NET and C#.

Dan Hurwitz

MSDN Magazine February 2003

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend