Drew Wutka
DWUTKA at marlow.com
Sat Feb 1 23:31:01 CST 2003
Actually, I didn't come 'from' the programming world. I was just raised around computers, been using them since I was 5. So I always found it easy to pick computer stuff up. I taught myself Access, and a few months into that I began teaching myself VBA, because macros can only go so far. I know what you are saying though, so I can't argue the logic. However, I would be far less resistant to letting a Server side DB do things like that for me, then a Client Side db. Don't get me wrong, I love Access. In fact I like to push Access to the limits, and beyond when I can get away with it. However, in doing so, I need it to be lean. I certainly have NOTHING against using tools like RI, or bound forms, etc. In fact, on occasion, I use them myself. However, most of the stuff I do is designed for relatively heavy use, so I keep Jet doing only data reads/writes. I don't want it doing anything else. But that is just the stuff I am working on. Everyone has their own 'markets' or customer base, and thus their own development 'traits'. Drew -----Original Message----- From: John Bartow To: accessd at databaseadvisors.com Sent: 2/1/03 8:36 PM Subject: RE: [AccessD] Cascade-delete (was: Estimating Help) I've always seen this as the difference of where you come from, ie. db administrator or programmer. A db admin would want it in the db so that no programmer can miss the logic and screw things up - a programmer would want to do it in code. I came from the DB admin. of Informix on Unix and I had a DB where the ref. int was ignored by the original programmers because they were going to do everything themselves. Problem is they weren't the only programmers and things don't stay static. It was a night mare. So I look at it as this is the "way it should work for everyone who uses this DB and no one gets around that. In the case of cascade delete I certainly don't use it on everything but in the obvious case of where the business rules allow a record to be deleted - use it so that all of the records child tables are cleaned up when it is deleted. As far as cascade updates - they aren't needed when using auto # keys but certainly are when using "natural keys", e.g. keys that can be broken and will need to fixed because the system didn't use auto # keys to start with ;-) Referential integrity - its great! -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Drew Wutka Sent: Saturday, February 01, 2003 3:53 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Cascade-delete (was: Estimating Help) Just my two cents here. I personally build my own business rules into the front end, or the middle tier. I don't like 'automatic' processes that I haven't built personally! <VBG> I think of it along the same lines of tghe B vs. UnB issue. It's there, and I can see it's use, I just prefer to control things on my own. Drew -----Original Message----- From: Jeanine Scott [mailto:jscott at mchsi.com] Sent: Saturday, February 01, 2003 3:05 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Cascade-delete (was: Estimating Help) Yes, I have been lucky. :) All the databases I've designed (with the exception of my very first) I've locked the user's totally out of the backend. They can only do what I give them security to do with the exception of one power user that I've really (and I stress really!) trusted. I supposed I'll be one of those that has to be burned before I follow the path of wisdom. :) I definitely can see that situation you described happening if you have a project where the client isn't willing to pay for the administrative interface. Jeanine Scott Sr. Systems Analyst Spindustry Systems 515-669-2074 jscott at spindustry.com CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message including any attachments. -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of John W. Colby Sent: Saturday, February 01, 2003 2:43 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Cascade-delete (was: Estimating Help) Some of us are just luckier than others I guess. Never had a user rip the guts out of your database by trying to delete a client that they "weren't doing business with" at the moment. I should have such users! ;-) John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com