Howto Programming Three-tiered Object Oriented?

[RedLion]

Hello,

Everybody is speaking about Object Oriented and Three-tiered applications. And everybody can speak about it realy nice, but when you come to the reality everything is on an other way, the question become how to bring the theory in practice?

On the bottom we've got the Database, and the layer above we got the business logic and the last layer is the interface.

[business logic]
A normal object is a Person. It has a name and adress as the properties. On that properties you can let methods work. GetName(), SetName() and so on.....

But now we've got a database with 1 million records. What to do now?
Read all records out a Database and define an array of 1 million person objects? Or should you say I define one class only with methods, and my properties are still in the database? When I need some data I use a sql-statement and put the selected data in a Cursor which gives the Cursor to the Interface layer, and the Interface layer fills the grid with that information?

This is a thing where object oriented sounds nice but how to implement it in the real world?

Thanks,

Charl

 

[foxdev]

FWIW, in the editorial on the most recent FoxPro Advisor, the author said "You can and should be using multi-tier designs in your pure VFP applications ..." (emphasis mine)

http://www.advisor.com/Articles.nsf/aid/BOOTJ06

Robert Bradley

http://www.foxdev.com/