C-Sharp (C#) Group: Business Logic versus Web Service

I am a little confused about what should go into the
business logic
layer? I am redesigning an application for one to build a
more robust
application / web application than what is currently in
place. The
previous coder used both business logic and web services but
seems to
have similar information in both. For instance: One such
method is
Login. I can see using a web service for the Login method
using Soap
Headers but if I do most of the methods in this manner there
won't be
too much in the Business Logic. The application that I am
redoing is an
asset management and problem tracking/ticketing system. The
few things
that I can see going into business logic are such things
like a ticket
if being created for as asset much have asset information.

If anyone can point me in the right direction or provide any
helpful
resources that would be great. 

Thank you in advance...

SBProgrammer

In a 3 tier application (presentation, business logic and
data access)
the names of the layer basically sum up what you should find
in each
layer:

i.e.

all presentation logic should go into the presentation layer
(it is
important to try to separate this layer from the business
layer as
redesign becomes at lot easier later on)

the data access layer (dalc) should contain all logic that
is needed to
access the database, in you case im would assume that the
web service
would be interfacing with the dalc

and basically all other code apart from the service logic
should go
into the business logic layer (this should include
application wide
classes, helper classes, and other global classes that need
to be used
by multiple layers)