Rohit, He is absolutely correct with respect to oracle as rdbms and lets say oracle forms and reports as front ends with or without any application server. eg lets say there are ten different types of purchase orders and they require some business rule validations and such validations are written in all these ten forms, Some time latter this business rule has been changed, now you will have to change all these ten forms along with changed documentation..Now instead this heavy exercise if you write a single procedure, you need to change only this procedure all the ten forms will have changed rule.. Yes, what Andre is saying is true, it is possible that if application is integreated with some legeacy data or application then these proecedure may fail. Usually such cases happens when new codes or some master data is changed/added into legeacy application and that has not been taken care in the present new application or interface or the interface between legeacy application and present application could not understand the changed/new data/value/elements in legeacy..This is a known risk..which can be overcome 0)if documentation exists for your present application and either exists or prepared for legeacy applications as well, in short system study of both the application is mandatory. 1) decide a cutoff period for legeacy application and design a brand new module/functionality/application as a extention of the existsing application. Thanks! Subodh On 8 November 2010 19:21, RP Khare <passionate_programmer@xxxxxxxxxxx>wrote: > Hi, > > > I read Tom Kyte's "Effective Oracle by Design". There he says to write most > of the code in the DB itself to reduce application code. It is good in a > distributed environment, but is it advantageous in an standalone application > also? > > My app. is in .NET. > > > > ................ > Rohit. > -- ============================== DO NOT FORGET TO SMILE TODAY ==============================