Re: A philosophical newbie issue: catch redundant errors via relationships or programmically?
From: Marshall <marshall.spight_at_gmail.com>
Date: Sun, 30 Dec 2007 11:45:44 -0800 (PST)
Message-ID: <d1897ed0-3c95-4bc9-b745-5c583fe1dc94_at_e25g2000prg.googlegroups.com>
> BTW, I notice a tension between not just front end GUI and back end dB
> schema people, but between putting data traps and data crunching code
> in the GUI front end versus writing a SQL query or otherwise dealing
> with the data in the back end. In fact, some people (the posters at
> microsoft . public . access . formscoding and elsewhere) imply and
> state that it's better to deal with this stuff at the front end, since
> SQL "puts too much load onto the servers" (or in particular Access), a
> preformance issue, while others, I suspect you guys, think that the
> front end technique is too much of a maintenance problem or is bad
> design.
Date: Sun, 30 Dec 2007 11:45:44 -0800 (PST)
Message-ID: <d1897ed0-3c95-4bc9-b745-5c583fe1dc94_at_e25g2000prg.googlegroups.com>
On Dec 30, 9:09 am, raylopez99 <raylope..._at_yahoo.com> wrote:
>
> BTW, I notice a tension between not just front end GUI and back end dB
> schema people, but between putting data traps and data crunching code
> in the GUI front end versus writing a SQL query or otherwise dealing
> with the data in the back end. In fact, some people (the posters at
> microsoft . public . access . formscoding and elsewhere) imply and
> state that it's better to deal with this stuff at the front end, since
> SQL "puts too much load onto the servers" (or in particular Access), a
> preformance issue, while others, I suspect you guys, think that the
> front end technique is too much of a maintenance problem or is bad
> design.
If you want wrong answers quickly, then by all means enforce data integrity in the front end.
Marshall Received on Sun Dec 30 2007 - 20:45:44 CET