> the day you have 2 stored procs that update a > common set of tables is the day the wheels > have come loose I really fail to see how you can say that this is always true. We write distinct functions and procedures to do distinct tasks - whether in a client application, 'nth tier', or stored procedure on the database. The fact that they operate on the same tables is not in itself an indication that the "wheels have fallen off" - IMHO of course. Paul Ritchie. --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi"
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Myles Penlington
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. David Brennan
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. Neven MacEwan