Re: system interface transactions

Responding to Timasmith...

So I have an elaborate schema with tables such as
PATIENT
ADDRESS
ORDERS
etc.

This is a Data Modeling description. If you are doing a RAD development for CRUD/USER processing, this is probably not a good forum for this question because the OO paradigm is usually overkill in CRUD/USER situations.

If your application will solve a more complex problem than typical CRUD/USER processing, then you need to solve that problem first and then worry about how the data will be persisted. That is, access to persistence will usually be encapsulated in a low level subsystem within the application. So thinking in terms of RDB tables for the problem solution will just lead to a poor OO solution.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
(888)OOA-PATH



.