Jim,

>Not one word of what you said has anything to do with N-Tier. You can build an N-tier system design in VFP today and then simply replace the UI tier sometime later with an HTML layer and you will have an internet application. The whole idea of N-Tier is that I don't have to know what I might want later on any tier in order to build a functioning app today that will be able to be enhanced later for expected and unexpected requests.

Well, It seems that i've read your message in the wrong way; sorry for the confusion. What i was trying to say, of what you don't know, you can't build a framework.

In this I agree. A good design of the framework would give you maximum flexibility. I still tend to write 3-tier applications (data - buisness logic - gui). But I'm curious about your opinion: how should the business logic be implemented, and what do you consider business logic ?

For example:
- you might create objects that act like the business logic layer or create the the business logic in the DBC container in the form of a stored procedure.

- You can have a printing routine in the gui layer or in the business objects layer.

Personally I still doubt about what belongs where and how it should be implemented.

Walter,