Infopath. webservice and SQL

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Papanii - 01 Jul 2004 17:34 GMT

Hi,
I am currently building a InfoPath form which will communicate with a
database. This form will be submitting and receiving data to and from the
database. A couple of weeks ago, I read a article in September's issue of
MSDN magazine which was edited by Nancy Michell. She stated that it would be
better to have a webservice in-between a database and a InfoPath form.
Unfortunately she didn't state why this approach would be better than having
the form directly access the database. However she did state that the direct
access should be avoided whenever possible. Why I don't know. Could someone
please elaborate on this topic for me?

--newbie

Reply to this Message

Roger Jennings - 02 Jul 2004 04:44 GMT

The issue of isolating the data access layer from the presentation layer
(InfoPath, in this case) is a combination of architectural preference and
application design "best practices." I use Web services primarily when users
must obtain and update data over the Internet or an intranet segment that's
isolated from the database's segment. The example that at
http://www.oakleaf.ws/InfoPath/nworders.aspx requires Internet access.

If your InfoPath clients have direct network connectivity to the database,
there's no significant benefit to using a Web service; a Web service adds an
easily mesurable performance reduction.

--rj

> Hi,
> I am currently building a InfoPath form which will communicate with a
[quoted text clipped - 8 lines]
>
> --newbie

Reply to this Message