In Brief
InfoPath 2003 is not always the best solution to problems that can be solved with XML-based forms.
InfoPath 2003 is limited in the complexity of joins when accessing RDBMS back-ends, when compared to Access projects or custom solutions.
Take time to define the business information need that an InfoPath solution is intended to solve. When appropriate, discuss information needs with colleagues to ensure that all relevant information needs are identified.
Document use cases for all but the most trivial InfoPath solutions.
Plan training needs for users to ensure the smooth and effective deployment of InfoPath solutions.
Make sure you provide user documentation, both online and on paper, to help users enter data that is complete and of excellent ...
Get Microsoft® Office InfoPath™ 2003 Kick Start now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
