Re: But a fool with a tool is still a fool


"Jim Cooper" <jcooper@xxxxxxxxxxxxx> wrote in message
news:44030b10$1@xxxxxxxxxxxxxxxxxxxxxxxxx

If you think I prefer to use an OPF because it's cool, you're very
mistaken.

Not at all, but it is cool :). In re-designing our system for .Net, we need
a underlying mechanism to 'manage' the relationship between the business
processes. The design patterns used in OPF is ideal *and* cool. The only
troubling area I have is SQL code maintenance. Not necessarily by me, but
how creative other developers get in writing SQL in code (ex. the earlier
SQL sample I posted) and while 'it' works today, tomorrow, 6 months from now
something is going to blow up (in the example I posted, it did). From a
consultant point of view, code blowing up is great news (get to come in and
charge more $$$), but I'm too lazy for that. When I write the invoice
creation object for .Net, I never, ever want to get into that code to figure
out why sales tax isn't getting charged (I open up the stored proc, look at
the data, fix it on the server, I'm done).
I can't post the exact code here, but this kind of code is inside our
*international* web site..

if Country = 'US' and State = 'MO' then {yes, hard-coded US and Missouri for
an international web site }
begin
{code to calculate shipping restrictions}
end
else
begin
if Country = 'NA' and State <> 'MO' then
begin
{logic to calculate shipping restrictions for Norway and not in
Missouri, I have no idea why MO is in there}
end
else
begin
{snipped all the other 28 other countries in the nested
if..then..else}

end

If the developer had placed the business logic on the server (each country
has some specialized logic), we wouldn't have gotten into a legal mess (I
can't get into it on a public forum). Even though what and how he was doing
it was wrong, if the code was on the server, more than one set of eyes could
have discovered the problem and fixed it without the US government getting
involved (it wasn't until we were fined when the developer took the warnings
seriously). The 'I can't reproduce it on my machine' excuse only goes so
far.

krf


.

Relevant Pages

  • Re: Linked Server Security
    ... security flaw) by creating a sql user on the dev box that did ... corporate db security because of a developer who used his sql login to ... create a linked server on a box he manages. ... However, before you do this, I suggest that you request that this developer ...
    (microsoft.public.sqlserver.security)
  • Re: SQL server 2000 C/S
    ... The developer edition of SQL is exactly for that, ... Same with the applications and client tools. ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: SQL 2005 Tools
    ... does he want the developer to work on the server, ... things yet he requested the password from me to access the server and poke ... been added to system databases and he created a new database as well. ... You'll need to enable the ports and protocols using the SQL Server ...
    (microsoft.public.sqlserver.connect)
  • Replication on W2KP
    ... I have an application which was developed on SQL 2000. ... experiment with setting up live replication, ... took a snapshot of my database to put on the developer editions of SQL ... 2000 server which are running on my portable and desktop computers, ...
    (comp.databases.ms-sqlserver)
  • Re: linked sql 2000 tables in access and create table statement
    ... Access isn't the best tool to use to create SQL Server objects. ... You can obtain the Developer ... >or should I be developing in Query analyzer or the query builder in enterprise manager? ...
    (microsoft.public.access.externaldata)