Swordsy
Guest
|
 Posted:
Thu Nov 10, 2005 9:51 am Post subject:
Forms development with Sharepoint Portal Server |
|
|
Hi, I'm a newbie in this forum and I have a question for those who are
using Sharepoint Portal Server (2003) as a backbone for data entry
forms (for such tasks as requesting leave, requesting to book a flight
etc.).
I have a strong background in ASP/SQL Server development and I'm
competent in developing web pages for data entry and the database
structures to go with them. However, my organisation has started using
SPS and company policy is tending towards using the portal for as much
as possible. The range of technological possiblities with regard to
developing straighforward data entry forms has me confused, so far I
can identify the following:
-Sharepoint lists
-Infopath/Sharepoint lists
-Sharepoint Web Part pages using the form web part
-Sharepoint Web Part pages built using form pages developed in Front
Page 2003
-Web Forms developed from scratch in Visual Studio.NET whilst storing
data in SQL Server and simply grafted into Sharepoint using the Page
Viewer web part
I would like to avoid re-inventing the wheel wherever possible whilst
maintaining flexibility and I feel that I am missing the point a little
when it comes to how Sharepoint and Infopath fit into a data entry
strategy. Some advice on the pros and cons of the different approaches
would be greatly appreciated.
Thanks |
|
Gary A. Bushey [SPS MVP]
Guest
|
| Posted:
Thu Nov 10, 2005 1:50 pm Post subject:
Re: Forms development with Sharepoint Portal Server |
|
|
InfoPath works great as an XML based data entry tool. It can update itself
from lists stored on SPS (or other data sources). Perhaps the biggest
drawback is that anyone who wants to use the forms needs to have a copy of
InfoPath on their desktop machine. SPS is already setup to store these
forms and can even combine the information from multiple forms into one
view.
ASP.Net web pages would probably take longer to develop but you would not
need any additional software to use them.
Depending on the complexity of your data needs a SPS list would be easy to
use and would not require any additional software but they are severely
limited as to what they can do.
--
Gary A. Bushey
SPS MVP
bushey@mindspring.com
"Swordsy" <sean.swords@gmail.com> wrote in message
news:1131614563.636224.185250@g49g2000cwa.googlegroups.com...
| Quote: | Hi, I'm a newbie in this forum and I have a question for those who are
using Sharepoint Portal Server (2003) as a backbone for data entry
forms (for such tasks as requesting leave, requesting to book a flight
etc.).
I have a strong background in ASP/SQL Server development and I'm
competent in developing web pages for data entry and the database
structures to go with them. However, my organisation has started using
SPS and company policy is tending towards using the portal for as much
as possible. The range of technological possiblities with regard to
developing straighforward data entry forms has me confused, so far I
can identify the following:
-Sharepoint lists
-Infopath/Sharepoint lists
-Sharepoint Web Part pages using the form web part
-Sharepoint Web Part pages built using form pages developed in Front
Page 2003
-Web Forms developed from scratch in Visual Studio.NET whilst storing
data in SQL Server and simply grafted into Sharepoint using the Page
Viewer web part
I would like to avoid re-inventing the wheel wherever possible whilst
maintaining flexibility and I feel that I am missing the point a little
when it comes to how Sharepoint and Infopath fit into a data entry
strategy. Some advice on the pros and cons of the different approaches
would be greatly appreciated.
Thanks
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in