sharepoint database or directly to SQL

[dbj]

I am new to InfoPath and would like to have an opinion. I am developing a
line of business app that will use InfoPath and Sharepoint as its primary
interface. Taking into account any new functionality Office 2007 and
Sharepoint Server 2007 may have, should I develop a business app schema
using the Sharepoint data store (custom lists) or define my schema directly
in SQL and then expose that through Sharepoint? The schema requirements I
have are quite complex (over 250 objects) and has many associative tables
(many-to-many) and a few self related tables.

I know that the next release of Sharepoint (MOSS 2007) will allow lists to
be tied into outside sources. And we are of the belief that InfoPath Server
2007 will provide the data collection services we need. We just need to
know where we need to build the data store. Thanks.

Don

 

[Bob C.]

For a complex model like yours, I'd go with SQL Server as the store .vs SP
lists.

1) You can view your SQL lists in SP.
2) You;ll have more flexability (perhaps at the cost of complexity);
3) You can use Sharepoint for the Infopath Form Library, great for Workflow
and alerts (2007 builds on these features).

 

[dbj]

Thanks Bob for your insight.

Don

For a complex model like yours, I'd go with SQL Server as the store .vs SP
lists.

1) You can view your SQL lists in SP.
2) You;ll have more flexability (perhaps at the cost of complexity);
3) You can use Sharepoint for the Infopath Form Library, great for
Workflow
and alerts (2007 builds on these features).