[b]To "c" or not to "c": Code or controls with db creation?[/b]

[Quehay]

I'd like to solicit advice from the more experienced DB programmers:&nbsp;&nbsp;Outside of very particular and demanding situations do you prefer to use adodc controls or write code from scratch to create db,connection, recordsets?&nbsp;&nbsp;<br><br>(The purist streak makes me think that the men (& women) use code and the boys use controls but this may be untrue.&nbsp;&nbsp;It also seems that the effort of coding would give much better insight and control of the processes involved.&nbsp;&nbsp;At this point I'm just using the Jet provider and .mdb files, so the cookie cutter approach is probably the <i>easiest </i>solution.)

 

[DannyB]

Personally I prefer to always write from scratch. Although it's harder work, I get MUCH MORE FREEDOM !!!<br>I also build objects, so next time around much of the work is already done. It's also very easy to convert classes into all sorts of components !! <p> <br><a href=mailto: > </a><br><a href=

http://dba.8m.com>

</a><br>

http://dba.8m.com

 

[chiph]

I prefer to code from scratch.&nbsp;&nbsp;I get better control over the number of connections being made to the database.&nbsp;&nbsp;Which is important when you consider Oracle is licensed per connection.<br><br>Unless, you hook Oracle up to the Internet, then you pay per processor MHz.&nbsp;&nbsp;But that's only partially relevant to your question...<br><br>Chip H.<br>

 

[Quehay]

Thanks for your comments guys; you've confirmed my general sense. Writing your own seems irresistably elegant...now to find a reference source that addresses the vagueries of user entry and traps errors/bad data/wrong button,etc.