Paul McNary wrote: > I'm just working through the possibilities I am needing. I can see it as > being a 6 and 'half a dozen' thing. I comfortable with the dCursor API > but I can see the possibilities of using Biz objects. I'll play with > both methods and see where it leads me. These are simple lookups like > Drug NDC (ID #) to find a description, etc. The Drug files we purchase > have about 150 different tables in them. So I can see a Biz Object that > links a bunch of them together to return the info I need would probably > be nice.
I do it either way, sometimes defining a bizobj othertimes just executing the SQL through a TempCursor. Sometimes I even query the db directly not using the Dabo layer at all. For the simplest things, I find it is easier to use the python dbapi directly, as long as I can guarantee that I know what the backend database will be. At some point it makes sense to use the Dabo layer, and usually it just makes sense to make it a bizobj, even if I'm not coding any business rules. But whatever works at the time. If you need a refactor later, then it isn't tough to do. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
