Business Layer - Data Layer

Hi all,

I hope this is a suitable group for this question. Feel free to push me off to the correct one if not. :)

Basically i have been developing windows applications using Visual Foxpro for about 5 years for a small software house and we will be shortly moving to a .net (C#) solution.

Within our VFP applications there are no distinct application layers whatsoever. Business logic, data access / manipulation and GUI code is all lumped together on forms and program files. With our move to .net I would like to implement more of a 3 teir architecture with the UI, Business Logic and Data Access / Manipulation all separated out.

I understand completely the theory behind this, but am struggling somewhat to grasp the practical details. If, for example, I have a Client object in my Business layer, what would i need to do do access / update data based on the theory that the Business layer does not have any sql statements etc in it? Pass datasets between the two layers? Or xml / web services?

If someone could give me a point in the right direction or let me know of some good resources / books i would be most grateful.

Best Wishes,

David Gouge
.

Relevant Pages

  • Re: datareader vs. dataset
    ... Karl, ... business layer in our application (they return a TDS from the DAL. ... distince DAL/BAL using the custom entity approach as described in your ... how would you implement the data access and mapping using a separate ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Why we need business logic layer?
    ... data stores without upsetting the business layer. ... on the file system, or in the database. ... "old" database was, say, Oracle and the new one is SQL Server, your data ... layer would need to be re-written for different data access, ...
    (microsoft.public.dotnet.framework.aspnet)