Hi Denver, Good idea... I don't have an idea how much overhead keeping uncompiled code in the database and running it with indirection will bring though. Negligable?
> > Approval Types are just simple key value pairs in the database and that > > might eventually cause problems, I suspect... > Why? My code would depend upon the ApprovalID, which means that accidental manipulation of data would cause serious problems. As you stated and proposed this solution is keeping some "classes" (which are different approval types) in the database (codes and/or approval type hierarchy) instead of compiling all of the approval types as independent classes. Yes, this is more flexible, but the application built might be more vulnarable to data accidents... This might also effect the application portability, as I'll need to create exactly the same data if I want to reuse the code on another sytem. Thanks anyway, I'm more clear now, at least I now know that I'm not in the wrong way. Regards, Teoman
