hmm, orm or sp?
really?
how about a situation where the object oriented approach is the wrong way to go?
a friend has developed an application that is currently being used in a few medical clinics locally, methadone maintenance program only clinics. he has found that a procedural approach dramatically improves performance, and reduces the code complexity for the app.
and due to original client requirement, the db engine this thing uses is access. :/
interestingly enough, the "triplicate" prescription requirements of methadone are lower in security focus than the medical records are. :/
methadone, like a few other medications, requires a "triplicate" prescription form, which is a carbon copy of a prescription, on file in the patient's chart and available for reference if any questions are asked about that patient's treatment, by the authorities with legal access to the records.
