Has anyone employed InfoPath to
develop forms for an Access application,
and, if so, what are the strengths / weak-
nesses of Infopath when used in an
Access environment?
InfoPath doesn't have as much capability ("richness", "robustness") as
Access for application development.
Brendan is correct in his comments -- licensing costs, unless the company is
going to license InfoPath for other purposes, would be an unnecessary
expense (you don't have to buy many user licenses to pay for Visual Studio
Tools for Office 2003 to be able to deploy with the Access runtime).
There are, likely, some not-so-common application requirements that could be
satisfied with a combination of InfoPath, Jet, and Access, but I don't have
any clients or colleagues who've implemented such an application. I'd
hesitate to call it an end-user development tool and Access a developer's
development tool, because my initial views were that it might be a little
too technical for most end users.
Larry Linson
Microsoft Access MVP