> Aside from the obvious reason of keeping the db logic > inside of the db > and built in referential integrity, I was stumped. I > thought given > the relationships, sqlserver gets hints as to how to speed > up joins > and such. I've already suggested that different programs > that use the > data wouldn't have to recreate the integrity logic, but I > need > more.........or maybe I don't. Maybe it's fine to keep > this in VB?
I prefer, whenever possible, to not allow poorly designed apps (vb or otherwise) to allow orphaned records to hang out in the db for no apparent reason and slow everything else down while not providing any value. I've worked for companies where they preferred _not_ to be informed when their code was bad because their interpretation of the problem when a foreign key constraint was violated (and raised an error) as having been "caused by the constraint" rather than the reality that it was sloppy code that never bothered to consider referential integrity or for that matter even whether a record would _EVER_ be seen by a user or have an impact on the remainder of the application (beyond slowing database queries). s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:166813 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
