Well a web service is not going to add anything unless you have a specific
remit to solve that involves using webservies, such as different or
geographically split clients wanting to make use of a common data layer. If
the asp.net quickstarts are too low level for you, and they dont cover
design really - have a fish around for some good tutorials on multi tiered
web developement. Here's one to get you started:
http://www.johntimney.com/home/redir...le.aspx?id=515
--
Regards
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
"mscertified" <ru****@tigerlily.comwrote in message
news:55**********************************@microsof t.com...
>I looked at those pages and they are pretty basic and low-level. What I'm
looking for right now is guidance on how to architect this application.
For
instance someone suggested we use a web service. So I'm looking for
direction
on how to plan the overall structure of this application rather than get
into
details about how to program individual pages or controls.
David
"John Timney (MVP)" wrote:
>I think the first thing you should do is read the ASP.NET 2.0 quickstart.
Its a very useful guide for inexperienced asp.net developers.
http://www.johntimney.com/home/redir...artv20/aspnet/
Specifically lookout for the wizard controls and login controls in
relation
to what you describe below.
Regards
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
"mscertified" <ru****@tigerlily.comwrote in message
news:2E**********************************@microso ft.com...
I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out
various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and
then
post
the item 'job completed' and send it back to the original user. The
whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine
what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.
Thanks.