As I'm spending more time going through the tutorials, and helps and seeing how the system works, now I want to step back and look at SF from outside to inside, rather than jumping right into details.

Doing so, several fundamental questions have come up and I don't seem to find a clean cut answers to them. I had looked at many other OR mappers before or products that let you create 3-tier apps or discounted apps, using memory tables and so forth. Each vendor seem to have their own definitions of Business layer, business objects, tables and so on.



Now my humble request to SF team is to provide (and perhaps put it in the help as well) or point me to the right directions which defines the following concepts and also establishes relationships among them and where they fit.



We have:



a) Data Access Layer class

b) Business Layer class

c) Business Object class

d) Data tables

e) Views



What I like to know (before jumping into methods and properties) of each one, is to have a full definition of each. For example:

How is business layer and data access layer relate with each other?

What's Business object in relation with Business layer?

Is Business object simply a collection of rows with methods and events? Is it more like a disconnected memory table?

What's data tables in relation to Business object?

What's view in relation to data tables?



Thank you in advance!


..ßen

Sure.  One thing about the in-class training is that when you leave all of this type of information and logic is covered to the point that it is just second nature.  I recommend coming to the class in May if you get the chance!

That's exactly what I was thinking, as I was reading your post.

Let's see...

..ßen